Exceptions & reconciliation
Review, match, and resolve inbound credits and externally-initiated debits that can't post automatically.
Most money movement posts on its own. This section covers what happens when it can't — funds that arrive or debit requests that come in through external banking rails and need review before they're applied to an account.
When an inbound ACH or wire credit, or an externally-initiated ACH debit, can't be confidently matched to an account, PCE records it as an external transaction and holds it for review. You (or your operations team) confirm the target account and accept, correct, or reject it. This is a reconciliation layer that sits after money movement — not a payment method.
Happy path vs. exception path
When you share your account details for inbound funds, most credits auto-match and post — that's Funding instructions. The items that don't auto-match land here for review.
The two exception types
Inbound ACH and wire credits received on your routable details. Match and accept them (ACH can also be rejected; wires are corrected and accepted).
Externally-initiated ACH debit requests against your account. Review, then accept, reject, or reassign for further review.
See also
- Funding instructions — share your details so inbound credits arrive (and mostly auto-match)
- Transaction lifecycle — the shared status model for money movement
- External Transaction Handling Error Codes — resolve a failed accept, reject, or reassign
Updated about 15 hours ago