IBOR ABOR Reconciliation: Automating the Match to Your TPA

NeoXam Aro reconciles the Investment Book of Record (IBOR) against the Accounting Book of Record (ABOR) automatically. It clears expected differences before an analyst is involved, ranks what remains by fund impact and routes genuine breaks to the right person with context already applied. The team works only on the exceptions that matter.

Why IBOR and ABOR Differ

Most asset managers work from more than one view of the same portfolio, an investment book and an accounting book, and every day those views are reconciled. The IBOR reflects what the front office sees: positions, cash and exposure updated in real time as trades happen. The ABOR reflects what the TPA has posted, settled and signed off at a point in time, end of day. The IBOR takes a forward-looking, trade-date view that accounts for cash ladders while the ABOR relies on settlement date.

Both are correct. Both are incomplete pictures of the other. Almost every difference between them is expected. 

Differences are expected in Cash Balances and Total Equity on Futures/CFDs, but we can explain them by looking at an account view. 

The risk is the one difference that is not expected. Because the NAV is struck from the ABOR, an undetected break can feed straight into the published price, which is what makes this recon a fundamental control and not just an exercise.

For the definitional comparison across all three books of record, see IBOR vs ABOR vs PBOR

Who this matter to

• Fund operations and middle office teams running the daily match to the administrator
• Heads of operations accountable for break volumes, aging and SLA performance
• NAV oversight and fund accounting teams validating the administrator’s figure before sign-off
• Asset owners and insurers who have outsourced accounting but retain the control obligation
• Internal audit and compliance who need evidence of how each break was resolved

How NeoXam Aro Automates IBOR ABOR Reconciliation

Clearing Expected Differences Before Anyone Looks

The hardest part of an ABOR to IBOR match is that the two books rarely line up one-to-one. A single ABOR position can net against several IBOR lines. Aro’s comprehensive match rules can reconcile complex items, like many-to-many matches, resolving those in a single pass instead of raising each one as a false break for someone to unpick by hand. That removes a category of false breaks before anyone looks.  In addition to applying rules, AI helps users review reconciliations when rules are incomplete or data quality is poor. It suggests matches and identifies breaks, helping speed up manual review and matching.

Ranking Breaks by NAV Materiality

Every break that does remain is scored by NAV materiality and flagged RAG, so teams work the highest-impact exceptions first and a rounding difference does not compete for attention with a break that moves the NAV.

Unresolved breaks are tracked and aged across daily runs, so a break that persists is followed from day to day with updated NAV Materiality rather than raised fresh each time.

Analysts spend their time on true exceptions. Aro has already cleared the noise.

Routing and Resolving with Intelligent Process Automation

Without automation, every break lands directly in an analyst’s inbox as a raw exception with no context or ownership applied. The analyst opens it, works out what it is, decides who should look at it and begins investigating. Across hundreds of breaks a day, most of that time goes on work a well-configured system could have done already.
Aro’s Intelligent Process Automation (IPA) applies your business rules to every residual exception the moment matching completes:

1. Each break is classified by type and reason
2. Where the resolution is clear Aro can automatically connect to the source system via API and resolve the break.
3. Where it is not, the break is assigned and routed to the correct team for review with context already applied.
4. When a reconciliation has no breaks at all, IPA workflows can auto-approve it with no manual sign-off and a full audit trail.

By the time an analyst sees it, the break is either resolved automatically or already has an owner, a type and a priority. The analyst starts from a prepared case, with the low hang fruit already removed. Everything IPA does is recorded, so the path a break took is always visible.

Analysts stop investigating from scratch and start reviewing the decisions Aro has already made.

Month End Reconciliation Without the Manual Process

Daily recons keep the two books aligned through the month, but fund operations teams also need a confirmed position at month end, and that works differently. Aro can be configured to treat month end as a distinct process: it starts with the daily recon at month end then splits into a parallel process where the daily and month end recons run separately but stay linked through shared break comments and updates.  The daily recon continues as normal and month end updates as relevant data is processed, so the team never restarts from scratch when a new file drops.

See month-end reconciliation for the full period-end process, and the month-end readiness checklist for T+1 considerations.

What Operations Teams Get

Front office and TPA work from data they can trust.  Aro gives both sides a daily view of where IBOR and ABOR agree, where they differ and why.  The investment team and the accounting team share a reconciled view of the portfolio, and the differences between them are documented and explained.

The operational impact is straight forward:

• Your team knows every day where IBOR and ABOR diverge and why.
• Breaks that need a decision arrive ranked by fund impact, with classification and context already applied.
• Clean reconciliations sign off automatically. The ones that need a person get opened; the rest do not.
• The same rules handle every additional recon as the fund range grows.
• Every break, comment and resolution is on record for internal review, client reporting or audit.

When the auditors ask for evidence, the answer is already there.

Related Reconciliation Capabilities

• No-code reconciliation platform — configure new reconciliations without IT
• Automated reconciliation and exception management — the matching engine behind the IBOR ABOR control
• Reconciliation dashboards, reporting and audit trails — RAG status, SLA monitoring and evidence
• OTC derivatives reconciliation — aligning IBOR and ABOR views on complex instruments
• NeoXam IBOR — the investment book of record itself

See IBOR ABOR Reconciliation in Action

Manual reconciliation slows your team down and leaves room for the one break that matters to slip through. NeoXam Aro clears expected differences automatically, ranks genuine breaks by fund impact, and gives your team a full audit trail from day one.

Talk to NeoXam to see how Aro can automate IBOR ABOR reconciliation for your fund range.