Why it matters for manufacturers
- A supplier can invoice the wrong entity, which puts GST credits and cost in the wrong place.
- Group-wide suppliers such as steel and gas are bought on one agreement but billed to several plants.
For manufacturers in Sage 300
- Intercompany Transactions is a separate module. One entry posts to each company it affects. ICT Accounts Payable covers invoices, debit notes, credit notes and interest charges.
- Set up routes between companies. A route can pass through intermediate companies and you choose it when you enter the transaction. Different companies can have different year-ends.
- Pick an A/P Clearing Account for each company on the ICT Options screen. The clearing account has a zero balance once the batches have posted to the general ledger in the originator.
- Posting checks fiscal periods. A locked General Ledger period stops the batch and creates an error batch.
What Sage 300 does on its own
Each company in Sage 300 is its own database. The Intercompany Transactions module lets you enter one AP invoice or GL journal in an originating company and spread it to other companies through a route. G/L Consolidations combines ledgers for group reporting.
- Setup is heavy: routes, distribution sets and tax accounts.
ICT is activated only in the company that originates transactions, not in intermediate or destination companies.
What you need and the setup steps: Multi-entity accounts payable for Sage 300.
Example
Example Gas Supplies sends one invoice covering bottled gas for Plant 1 in Sydney and Plant 2 in Brisbane, which are separate entities.
| Line | Amount | What the check finds |
|---|---|---|
| Gas cylinders, Plant 1 Sydney | $3,200.00 | Bill to Example Manufacturing East Pty Ltd |
| Gas cylinders, Plant 2 Brisbane | $2,100.00 | Bill to Example Manufacturing North Pty Ltd |
| Cylinder rental, shared | $300.00 | Split by agreed ratio |
Each plant's cost is coded to its own entity and shared rental is split by the agreed ratio. Each entity claims only its own GST.
Common mistakes
- Entering the whole invoice in one entity and fixing it later with an intercompany journal.
- Using different supplier names for the same supplier in each entity, so group spend cannot be added up.
Step-by-step guides for Sage 300
What Pulsify adds
Pulsify gives each company its own address, suppliers and approval rules, with one login across all of them. Pulsify connects to Sage 300. We set up the connection for you. More about multi-entity accounts payable in Pulsify or Pulsify for manufacturers.
More help
- Multi-entity accounts payable in Sage X3 for manufacturers
- Multi-entity accounts payable in SAP B1 for manufacturers
- Multi-entity accounts payable in S/4HANA for manufacturers
- Duplicate invoice checks in Sage 300 for manufacturers
- PO matching in Sage 300 for manufacturers
- Supplier price checks in Sage 300 for manufacturers
- Invoice approvals in Sage 300 for manufacturers
- All Sage 300 how-to guides
Sources
Last checked 2026-10-19.
Common questions
Can one Sage 300 entry post an invoice across several companies?
Yes, with the Intercompany Transactions module. An ICT Accounts Payable batch posts the invoice, credit note or debit note to each company it affects. You pick a route between companies when you enter it. The A/P clearing account ends at zero once the batches post.
Should each entity have its own supplier record?
Usually yes. Give each entity its own record for the supplier, with the same ABN, name and terms. Matching names let you add up group spend on one supplier without mixing the books.
Do I need separate Sage 300 databases for each company?
Yes. Each company has its own database. Intercompany Transactions uses an ICT company database for originating transactions.
Pulsify setup guides
Want this done for you?
Book a call to see how Pulsify handles multi-entity accounts payable in Sage 300 for manufacturers.