Overview
A Composite SOR combines records from two or more connected systems into a single source of record. AI Agents read from it the same way they read from a single system. The AI Agent will then work with vendors, bills, purchase orders, and payments that live in different systems.
A Composite SOR is a consolidation layer, not a connection to an outside system. It merges records, does not clean or enrich them. It asks for no credentials of its own. Each contributing system is connected and syncs on its own first, so a composite has nothing to read until at least two connections exist.
The merged result is stored as a source in its own right. Consolidated records sit in Auditoria alongside the records they were built from, so a composite adds a copy of the data rather than only a view over it.
When to use a Composite SOR
A Composite SOR fits where AP records are split across systems but the work is run as one desk.
Table 1. Common configurations
| Configuration | What it looks like |
|---|---|
| Multiple ERPs | One system holds financials and another holds procurement, and vendors and invoices are needed in one view. |
| An ERP with a separate AP system | One system is the ERP of record while invoices are processed in another. |
| Regional ERPs | A different ERP in each region, with AP run centrally. |
| Transition after a merger or acquisition | Two ERPs run side by side until the organizations consolidate. |
| A file-based ERP alongside a connected one | One system exchanges files through the Universal Connector while the other connects through its API. |
Note: A Composite SOR is not the right choice when a single system already holds all the AP records. It also cannot help when the systems share no common identifier. Matching needs a shared vendor ID, tax ID, invoice number, or purchase order number. Where the systems are due to be consolidated within about six months, connecting the surviving system on its own is usually the shorter route.
How a Composite SOR works
Contributing systems
The connected systems a Composite SOR reads from are its contributing systems. Select two or more. The list shows every ERP and AP connection on the tenant; check it against the supported systems in Table 3. A Composite SOR cannot contribute to another Composite SOR.
Each contributing system keeps its own connection and its own credentials. Removing a system from the composite does not delete the connection.
What each contributing system must supply
Each contributing system is read on its own. Records from one system are matched to the vendors and entities of that same system, never across systems. Every contributing system must therefore supply the full chain: its entities, the vendors tied to those entities, and the bills tied to those vendors.
A system that supplies bills but no vendors and entities of its own has nothing to tie those bills to, and its records cannot be placed in the composite. This applies to each system added later in the same way it applies to the first two.
Business record source mapping
The source mapping sets which contributing system supplies each business record type. The record types are Vendors, Bills, Purchase Orders, and Payments. Select the record types for each contributing system in turn. Every contributing system needs at least one record type before the composite can be saved. A record type with no source contributes no records to the composite.
More than one system can source the same record type. Bills can come from the ERP and from the procurement system, for example, and both feed the same composite.
Duplicate records
When the same record reaches Auditoria from more than one contributing system, only one copy is kept in the composite. Records are matched on the record identifier each source system supplies. Auditoria keeps the record from the primary system for that record type and skips the duplicate.
Matching only works where the systems agree on an identifier. In practice that means a shared vendor ID or tax ID for the same vendor, and an invoice number with its vendor, or a purchase order number, for the same invoice. Where the systems use different identifiers, a cross-reference the client maintains can supply the link instead. Entity structures should be comparable across the systems for the same reason.
Workday is the default primary system. If your composite does not include Workday, ask Auditoria Support to set the primary system for each record type.
Write to SOR
Write to SOR controls whether invoices processed in Auditoria are written back to a connected system of record. It is optional. When it is selected, one contributing system is chosen as the write-back target, and every invoice is written to that system. Workday is selected by default where it contributes.
Sync
Syncing a Composite SOR syncs every contributing system first, then combines the records. The contributing syncs run at the same time, and the composite is synced only after all of them finish. If any contributing sync fails, the composite sync does not run and the failure is recorded against the connection. Scheduled syncs follow the same order.
The composite drives the sync for the systems it reads from. Once a system contributes to a composite, the sync control on that system's own card is unavailable. Sync the composite to refresh the system. A system that contributes to more than one composite is refreshed by whichever composite syncs.
Supported products and contributing systems
Composite SOR is available for the accounts payable products.
Table 2. Product availability
| Product | Available on Composite SOR |
|---|---|
| AP Invoices | Yes, including write-back to the contributing system |
| AP Helpdesk | Yes |
| AP Accruals | No |
| AR Collections, AR Helpdesk, and AR Remittances | No |
| SmartResearch | No |
| FP&A Planning | No |
Table 3. Contributing systems
| Contributing system | AP Helpdesk | AP Invoices |
|---|---|---|
| Workday | Yes | Yes |
| Oracle NetSuite | Yes | Yes |
| Sage Intacct | Yes | Yes |
| Coupa | Yes | Yes |
| Universal Connector | Yes | Yes |
| Oracle Fusion | No | No |
File-based ERPs contribute through the Universal Connector. Set up the file exchange and confirm the Universal Connector on its own before adding it to a composite. A composite can pair a system connected through its API with a Universal Connector source.
Contributing Connected Systems lists every ERP and AP connection on the tenant, including systems that are not yet supported on a composite. Select only the systems marked Yes in Table 3.
Configure a Composite SOR
A composite is created like any other connection. For the full connection flow and what to check afterwards, see Connect Composite SOR.
- In the navigation rail, hover Administration, then select System Settings.
- Select Add New Connection.
- Select ERP, then select Composite SOR from the systems that branch out below it.
- Complete the fields described in Table 4.
- Select Save.
Figure 1. The Composite SOR Settings form.
Table 4. Composite SOR settings
| Field | What it sets |
|---|---|
| Composite SOR Type | The process the composite serves. Autonomous Procure to Pay (AP) is the available option. |
| Instance Name | How the composite is identified everywhere else in the product, including the SOR selector on every AI Agent. |
| Contributing Connected Systems | The two or more connected systems the composite reads from. |
| Business Record Source Mapping | For each contributing system, the record types it sources: Vendors, Bills, Purchase Orders, and Payments. |
| Write to SOR | Whether processed invoices are written back, and the contributing system they are written to. |
Business Record Source Mapping stays empty until contributing systems are selected. One card then appears for each system, with its record types beside it.
Figure 2. Business Record Source Mapping, with one card for each contributing system.
Selecting Write to SOR lists the contributing systems as write-back targets. Choose one. The Universal Connector option is unavailable.
Figure 3. Write to SOR, with the Universal Connector option unavailable.
Check the connection
The composite appears as a card on Connected Systems, with a row for each contributing system below its own details. The card is where you confirm that records have moved.
Figure 4. A Composite SOR on Connected Systems.
Table 5. What the card shows
| Field | What it tells you |
|---|---|
| Composite Instance Name | The name the composite is known by elsewhere in the product. |
| Initial Connection | When the composite was created. |
| Last Sync | Whether records have moved since the composite was created. A composite that saved cleanly but never synced shows a created date and no sync. |
| Token | The connection identifier to quote when raising a support case. |
| Used by | How many AI Agents depend on the composite. |
The rows below carry the instance name, last sync, and token of each contributing system, so a system that has stopped syncing is visible on the same card. To sync on demand, select the sync icon at the bottom of the card, which reads Initiate Sync Now.
Each contributing system also reports its composite use on its own card, as a count of the composites that read from it. Two controls on that card are unavailable while the count is above zero. The sync control is unavailable because the composite drives the sync. The delete control is unavailable until the system is removed from every composite that uses it.
Figure 5. A contributing system reporting the composites that use it, with its sync and delete controls unavailable.
Change a Composite SOR
Select Update on the card to change any field, including the contributing systems, the source mapping, and the write-back target.
To add a system to a composite that is already in use, connect the system first and let it sync. Then add it under Contributing Connected Systems and give it at least one record type. To remove a system, clear it from Contributing Connected Systems. Its card and its record types go with it, so check that every remaining record type still has a source.
A composite that AI Agents depend on cannot be deleted. Move the AI Agents to another source first. Deleting a composite leaves the contributing connections and the records in the underlying systems untouched, so a composite whose design turns out to be wrong can be removed and built again.
Limitations
- Composite SOR covers AP Invoices and AP Helpdesk. The other products listed in Table 2 cannot read from a composite.
- Records are matched on identifiers the source systems supply. Systems that share no common identifier cannot be consolidated.
- Records are merged whole. A record in the composite comes from one contributing system, and fields from different systems are not combined into one record.
- A composite does not clean, normalize, or enrich the records it merges.
- A system that contributes to a composite cannot be synced on its own. Sync the composite instead.
Related information
- For the connection flow these forms sit in, see Connect Composite SOR.