Skip to main content
Question

Construction Edition Parent Child billing, back to back AR invoice to AP bill creation

  • Nov 17, 2026 10:13 PM UTC
  • 1 reply
  • 5 views
  • Translate All

We have companies defined as branches. Each branch has it's own projects. 

Some projects done by branch companies are for other members of the group. 

We're looking at configurations of parent/child projects to handle this. 

Let's say company (branch) A handles the relationship with the external customer. It has two tasks that it bills to the customer. Company B handles the work for one of the tasks that company A will bill to the external customer. Company B will bill customer A for the work they performed. They are a profit generating company. 

The project in company B has expenses and revenues and invoices company A for their work like any other vendor does. Company A records the invoice from company B as if it is coming from any other vendor and it's a cost of their project.

I have defined parent child project relationships and parent child task relationship. Branch B has been extended as a vendor. Branch A has been extended as a customer. 

I ran billing in Branch B and an invoice was generated to Branch A. I ran generate intercompany documents in Branch A and it creates a project X AP bill and NOT a bill to their project (which I was expecting would be derived from the relationship between projects and tasks). 

The AP bill in company A hits only the expense account defined as the default for the company B vendor...it bypasses the external project coding.

It is not an option to have company B invoice the external customer because how company A gets the work performed is of no concern to the external customer

How do I automate the back to back project related AR invoice and AP bill in this scenario?

1 reply

Steve Milner
Varsity III
Forum|alt.badge.img+7
  • Varsity III
  • Nov 17, 2026 11:18 PM UTC

My replies are created in part with the help of proprietary AI, built with my AI skills, curated and maintained myself. Most replies are tested on local instances before they go up, and all are reviewed before posted.

@icook06 parent/child projects won’t drive this in 2026 R2. The release notes say your exact pattern (a child project acting as a profit center that bills the parent, with external billing staying at the parent) is planned for a future release. What shipped in 26 R2 is the parent billing for child cost centers, or the parent as a reporting container.

The task link is also working against you. Whichever Billing Project B’s project uses, a linked parent task in A is closed to AP. B needs Current Project to bill on its own, and with that setting every visibility check box on A’s task is cleared, AR included. Once no child task is linked to it, A’s task goes back to all boxes selected.

Two settings explain the bill you got. Generate Intercompany Documents (AP503500) puts the bill on the non-project code unless Copy Project Information to AP Document is selected. Even with it selected, it copies B’s project, task and cost code from the AR invoice. Nothing in that process reads the parent link. The account comes from Use Intercompany Expense Account From on Accounts Payable Preferences (AP101000). Vendor Location gives you the vendor’s expense account. Inventory Item takes it from the non-stock item on the line.

There’s no stock mapping from B’s task to A’s task. The closest you’ll get is generating the bills with Create AP Documents on Hold, then setting A’s project and task before release.

Here’s an idea we haven’t tested. Store A’s project and task on B’s project task, in a task attribute or a custom field. Then extend GenerateIntercompanyBillExtension, which is the AR invoice extension that AP503500 runs. In it, override GetAPTranProjectID and GetAPTranTaskID, plus GetAPTranCostCodeID if you use cost codes. Each of those methods receives the AR line, so it can find B’s task from that line and return the A values stored on it. Acumatica’s own intercompany sales extension overrides the same three methods to pull the project from A’s purchase order. Don’t use the Parent Task link as the lookup, because that link is what closes A’s task to AP. The account would still come from the AP Preferences setting. Try it in a sandbox first.

Translate