Skip to main content
Question

Is there a way to create a GL transaction based on sales order totals?

  • March 10, 2026
  • 5 replies
  • 36 views

Forum|alt.badge.img

Hi everyone,

Our business operates with four different branches. Our website allows single-cart checkout, meaning a customer can place an order containing items from multiple branches but only complete one payment at checkout.

That payment comes through as a single prepayment, which is posted to our Unearned Revenue account.

On the backend, our system then creates the appropriate sales orders for each branch (one sales order per branch). The single prepayment is applied across all of those individual sales orders.

Our question is:
Is there a way to associate multiple AR accounts with a single prepayment based on the branch of the sales orders tied to that prepayment?

Ideally, we would like the portion of the payment applied to each sales order to post to the AR account associated with that branch, rather than everything flowing through a single AR account.

Has anyone implemented something like this or found a workaround?

Thanks in advance!

P.S. we process thousands of sales orders so anything manual is not a possibility :) 

5 replies

ELIJAHRSWK07
Jr Varsity I
Forum|alt.badge.img
  • Jr Varsity I
  • March 12, 2026

Hey ​@SBaldwin I don’t believe this is supported natively. In Acumatica, a prepayment is a single AR document with one AR account/subaccount, even if it is later applied across multiple branch sales orders. If you need each applied portion to hit the AR account for that branch, the usual approach is either to split the payment by branch before creating it in Acumatica, or customize the process so branch-level reclassification entries are generated automatically.


Forum|alt.badge.img
  • Author
  • Varsity II
  • March 12, 2026

Hey ​@SBaldwin I don’t believe this is supported natively. In Acumatica, a prepayment is a single AR document with one AR account/subaccount, even if it is later applied across multiple branch sales orders. If you need each applied portion to hit the AR account for that branch, the usual approach is either to split the payment by branch before creating it in Acumatica, or customize the process so branch-level reclassification entries are generated automatically.

I thought that might be the case. 

So my thought was to build a GI that looks at all of the AR payments that came in the day before ( today()-1) and grab the applied to order amounts for those sales orders,. From that GI create an import scenario that is run every day to create journal transactions to transfer the funds from the general “Unearned Revenue” account to branch specific. 

Does this sound like a reasonable idea? It would require someone looking at the general account everyday if there are some funds that hadn’t been “transferred”


ELIJAHRSWK07
Jr Varsity I
Forum|alt.badge.img
  • Jr Varsity I
  • March 12, 2026

@SBaldwin 

Your approach is reasonable and is a pattern I’ve seen used in similar situations. The key is to base the GI on payment applications rather than just payments received the previous day. That way the journal entry only reclasses the amounts that were actually applied to orders tied to each branch. Any unapplied portion of the payment would remain in the general Unearned Revenue account until it is used.


Forum|alt.badge.img
  • Author
  • Varsity II
  • March 12, 2026

@ELIJAHRSWK07 great idea!! Would this information live in the ARAdjust Table?


ELIJAHRSWK07
Jr Varsity I
Forum|alt.badge.img
  • Jr Varsity I
  • March 13, 2026

@SBaldwin 

If you mean payment application to a sales order, I would start with SOAdjust rather than ARAdjust. ARAdjust is generally for applications against AR documents like invoices, while SOAdjust is the table that tracks payment/prepayment relationships at the sales order level.