Remittances in Confido post against a single customer. If you invoice at a more granular level — DC or banner — but only receive payment at the top-level account, you need parent-child relationships configured in your ERP.
Creating a new child customer in QuickBooks
1. Create a new customer record and name it appropriately (e.g., Kehe DC East).
2. In the Sub-customer of field, select the parent (e.g., Kehe).
3. Check Bill Parent Customer — this is critical. It ensures invoices post at the parent level rather than the child level, which is what allows Confido to see them.
4. Save the new child customer.
Migrating existing standalone customers to children
If DCs or banners are currently set up as standalone customers in your ERP (not as children), you'll need to migrate them. The process in QuickBooks is:
5. Create a new sub-customer under the correct parent (as above).
6. Go to the original standalone customer record.
7. Use Merge Contact to merge the old standalone record into the new sub-customer. This migrates all existing invoices and transaction history to the child, which now rolls up to the parent.
📌 Note: This merge is permanent. Confirm the parent-child structure is correct before merging. If you have existing open invoices on standalone customers, complete this migration before processing checks in Confido.
How do child customers roll up into forecast actuals?
This section is for QuickBooks Online (QBO) customers whose distributor DCs (distribution centers) or banners, such as UNFI East and UNFI West, are set up as sub-customers of a parent customer. When the parent/child relationship is set in QBO, invoice actuals for the child customers roll up to the parent in Confido automatically. You don't need to map each child customer in the Directory.
Can I see actuals at the DC level instead of the parent?
Yes. To bring in actuals at the DC level, map the child customer (for example, UNFI East) in the Directory. Each GL customer maps to one Confido contact, so mapping a child customer to the parent's contact removes that mapping from the parent. Mapping changes aren't instant: invoice actuals refresh once a day, so a new mapping shows in actuals after the next daily refresh.
Why don't my forecast and actuals match after DCs roll up to the parent?
Forecast and actuals won't match when actuals arrive at the parent but a Planning Group's routes to market (RTMs) are set by DC, such as UNFI East and UNFI West. In that setup, forecasted values split by DC while actuals sit at the parent. To fix the mismatch, set the Planning Group's RTM to the same level your actuals arrive at: the parent (for example, UNFI) if the DCs roll up, or each DC if you mapped them separately in the Directory.
Limitation: Confido can't show one customer's actuals at both the parent and the DC level at once. Workaround: Pick one level, and keep the Directory mapping and the Planning Group RTMs at that same level.