Intercompany: one sale, two companies' books

For the whole-system operator — you run the books. Level 3 — configure and own.

By the end you can set up the pairing that turns a sale finalised in one of your companies into the matching purchase in another, choosing the buyer’s own record, its account per company, the receiving branch and the rule, and choose it on each sale; then say what the second document copies, when it posts and what date it carries, work the confirmation queue and spot the pairings that failed, correct one side without breaking the other, and agree the two companies’ balances at month end knowing the group total eliminates nothing.

Before this series: Customers, suppliers and staff are one record, Companies, branches and dimensions, and what each one decides

Presentations

1. One sale, two documents: set up the pairing between your companies — about 8 minutes, narrated
2. The other company’s copy: what it carries, when it posts, and keeping both books in step — about 8 minutes, narrated

Modules this series draws on

• Core Module
• Sales Module
• Purchasing Module
• Financial Accounting Module

Reference pages this series draws on

Every screen a presentation mentions is documented on one of these pages; the series does not re-document it.

• Purchase Invoice (Internal)
• Reimbursement Payment Voucher Applet (Internal)
• Entity Maintenance
• Organization
• Supplier
• Purchase Credit Note (Internal)
• Sales Debit Note (Internal)
• Sales Invoice (Internal)
• Sales Invoice No Stock Out (Internal)
• Reviewing a Set of Books Kept in BigLedger
• What a Void Undoes
• Purchase Invoice Processing
• Setting Up a Group: What We Recommend

All presentations · Presentations for the whole-system operator