AP Reconciliation Agent. Four streams, one proven balance.

The standard JD Edwards AP reconciliation workflow, run by an agent. It proves the subledger posted to the G/L, ties the open balance to the control account, squares every supplier statement, and reconciles payments to the bank. Under the hood it calls named orchestrations on your AIS server and assembles Excel workpapers a Controller can sign. The agent prepares everything; a human approves anything that writes.

What the agent does

• Runs on close day +1 or on demand, scoped to your company set, period, As-Of date and bank accounts.
• Verifies the G/L period is open and holds the whole run if unposted AP batches exist, notifying the AP supervisor.
• Submits the three integrity UBEs (R04701, R04702, R09705), polls them to completion, retries once, then escalates to CNC.
• Builds the As-Of file (R04901A), runs the aged trial balance (R04423), and ties it to the AAI PB control account in F0902.
• Flags manual journal entries posted straight to the control account.
• Parses supplier statements (PDF or CSV) and matches every line against open and paid AP, with a fuzzy fallback on amount and date.
• Classifies what doesn't match: missing invoice, amount difference, unapplied credit, paid-not-cleared, dispute.
• Refreshes the bank rec workfile (R09510), auto-matches cleared items (R09511), and lists outstanding and stale-dated payments.
• Assembles Excel workpapers per stream, a variance summary, and a 14-type exception register routed to named owners.
• Executes a write (create voucher, void and reissue) only on a logged approval, then re-runs the stream to confirm it cleared.

Guardrails

• The agent is preparer only. A named human approves any posting, voucher, void, or adjustment.
• Read-only by default; WRITE orchestrations stay disabled without an approval token.
• Integrity runs at $0.00 tolerance. Timing items elsewhere use your configured materiality.
• Every run logs run ID, parameters, UBE job IDs and workpapers. SOX evidence by default.
• Re-runnable without side effects; write paths check for existing records first.
• Respects the period lock. A closed period is never touched.

Under the hood

Twelve named orchestrations built in Orchestrator Studio (the 59AP_ORCH_ catalog), called straight over the Orchestrator REST endpoint. No middleware in between. Read orchestrations run autonomously; the two WRITE orchestrations only accept a call that carries a logged human approval.