EdgeSync Docs
Resolve Exceptions
How operators review held paid bills, fix the underlying blocker, and retry safely.
Exceptions are paid bills that EdgeSync intentionally held because a required decision or mapping was missing. The goal is not just to show an error; it is to let the operator resolve it and retry safely.
Common exceptions
- Vendor not mapped between BILL and Financial Edge NXT.
- Distribution line is missing a required account, grant, project, department, or class.
- Financial Edge NXT rejected the posting because a dimension is inactive or not valid for the account.
- A duplicate invoice number, vendor, or payment reference requires review before retry.
Resolution flow
Operators review the exception, compare BILL source data with Financial Edge NXT requirements, choose or create the correct mapping, add an optional note, and retry the held bill. EdgeSync keeps the original source payload and records the resolution decision.
Retry rules
Retry is deliberate. A bill should only be retried after the blocking issue is resolved, and the retry should reuse the corrected mapping instead of creating a one-off posting workaround.