A RouteFusion prerequisite an otherwise-eligible org still has to satisfy
before it can be onboarded. Each maps to a concrete operator fix:
incorporationDate — no stored date. Fixable inline with a manual override
on the onboarding page (only when it's the org's sole unmet requirement),
or by editing the organization.
contactInfo — email, phone, or website is missing. RouteFusion hard-gates
email and phone (createBusinessEntity rejects without them); website is a
CFX policy requirement so the operator never has to supply it on
RouteFusion's hosted page. Fixed by editing the organization.
authorizedSigner — the org has no CONTROL related person. Every
CONTROL person maps to a RouteFusion is_signer representative, so an org
with none onboards into an incomplete KYB entity ("representatives
required"). Fixed by adding a control person on the related-people page.
businessAddress — the org's address is absent or incomplete (street,
city, postal code, and state/region are all required).
resolveRouteFusionEntityInput refuses to build an entity input without
them, so onboarding would fail at the entity create. The state/region in
particular is enforced by RouteFusion only at FINALIZE, so an org missing
it used to onboard cleanly and be refused at the last step. Fixed by
editing the organization.
representativeDetails — the org HAS related people, but at least one is
missing a field RouteFusion needs. toRepresentativeInput refuses to map
such a person (it used to substitute "", which RF rejects at its Email
scalar), so onboarding would fail at the representative push. Distinct from
authorizedSigner: that means no person, this means an unsendable one,
and they are fixed on different records.
A RouteFusion prerequisite an otherwise-eligible org still has to satisfy before it can be onboarded. Each maps to a concrete operator fix:
incorporationDate— no stored date. Fixable inline with a manual override on the onboarding page (only when it's the org's sole unmet requirement), or by editing the organization.contactInfo— email, phone, or website is missing. RouteFusion hard-gates email and phone (createBusinessEntityrejects without them); website is a CFX policy requirement so the operator never has to supply it on RouteFusion's hosted page. Fixed by editing the organization.authorizedSigner— the org has noCONTROLrelated person. EveryCONTROLperson maps to a RouteFusionis_signerrepresentative, so an org with none onboards into an incomplete KYB entity ("representatives required"). Fixed by adding a control person on the related-people page.businessAddress— the org's address is absent or incomplete (street, city, postal code, and state/region are all required).resolveRouteFusionEntityInputrefuses to build an entity input without them, so onboarding would fail at the entity create. The state/region in particular is enforced by RouteFusion only at FINALIZE, so an org missing it used to onboard cleanly and be refused at the last step. Fixed by editing the organization.representativeDetails— the org HAS related people, but at least one is missing a field RouteFusion needs.toRepresentativeInputrefuses to map such a person (it used to substitute"", which RF rejects at itsEmailscalar), so onboarding would fail at the representative push. Distinct fromauthorizedSigner: that means no person, this means an unsendable one, and they are fixed on different records.