Reconciliation and provider limitations
Bank reconciliation
Section titled “Bank reconciliation”Emissary supports explicit CSV, CAMT.053, and MT940 import profiles, matching suggestions, and confirmation workflows in tested subsets. It does not claim to parse every bank’s proprietary dialect or connect to a bank account universally.
A reconciliation suggestion is not a ledger change until an authorized decision is recorded. Refund requests and payment reversals also represent different facts.
| Connector | Jurisdiction | Status | Implemented capabilities | Validation notes |
|---|---|---|---|---|
| CSV / CAMT.053 / MT940 | generic | Ready | CSV subset import, CAMT.053 subset import, MT940 subset import, explainable reconciliation | Ready |
Provider connectivity
Section titled “Provider connectivity”Stripe tenant payment processing, Bizum acquiring, SEPA file submission, and regulated Open Banking access are not presented as generally available Production integrations. Provider account onboarding, credentials, external tests, legal status, webhook verification, reconciliation, and production activation remain provider-specific prerequisites.
| Connector | Jurisdiction | Status | Implemented capabilities | Validation notes |
|---|---|---|---|---|
| Bizum connectivity | ES | Under Evaluation | provider boundary, simulator classification | Under Evaluation |
| SEPA Direct Debit | SEPA | Under Evaluation | mandate record foundation | Under Evaluation |
| Open Banking AIS/PIS | EU/UK | Under Evaluation | consent boundary, provider integration point | Under Evaluation |