Shared Transactions - Shared Payments - Accepting Customer Payments on Behalf of Another Subsidiary
Overview
Shared Payments enables companies to accept customer payments in one subsidiary on behalf of another. The following walkthrough explains this process.
Step-by-step process
- Navigate to the desired invoice or create the new invoice via Transactions > Sales > Create Invoices.
- On the Custom tab select the desired company to collect the invoice payment in the field Shared Payment Subsidiary.
- Select Save.
- Once the invoice has saved a new subtab Shared Payments will appear. Here, you'll find the Shared Payments Journal that was automatically created.
- The Shared Payment Journal will be an Advanced Intercompany Journal that will appear as follows.
- Next, the customer payment can be accepted by navigating to Transactions > Customers > Accept Customer Payments.
- Select the Customer and the Subsidiary that will be receiving payment.
- Select the Shared Payment Journal Entry that was just created.
- Select Save and the payment will be created.
- Once Saved, the Shared Payment Journal will show the payment under the Related Records subtab.
- The original invoice will also show a status of Paid in Full with a link to the Shared Payments Journal on the History subtab.
Creating the journal when the customer pays
By default, Shared Payments creates the journal when you save the invoice and dates it to the invoice. To keep the receivable in the invoice's subsidiary until the customer pays, turn on Create Shared Payments Journal at Payment (AR) under Shared Payments Preferences on Netgain > Setup > System Setup. For the setting, see Shared Transactions System Setup.
The AR setting applies to invoices only. Vendor bills have their own setting, Create Shared Payments Journal at Payment (AP), and keep getting their journal when the bill is saved while only the AR setting is on. For the bill side, see Shared Transactions - Shared Payments - Paying Bills on Behalf of Another Subsidiary.
Step-by-step process
- Open the invoice, enter a value in the Shared Payment Subsidiary field and click Save. No journal is created yet, and the receivable stays in the invoice's subsidiary.
- Record the customer payment against the invoice in the invoice's own subsidiary, for example from Transactions > Customers > Accept Customer Payments. Do not apply it to a Shared Payments journal, because none exists yet.
- When the customer payment saves, Shared Payments creates the journal and dates it to the payment. It then changes the payment's subsidiary to the Shared Payment Subsidiary and its account to that subsidiary's, applies the payment to the journal, and closes the invoice. The payment keeps its customer.
The journal covers the full amount of the invoice, even when the first payment is a partial one. The reroute works for payments entered in NetSuite and for payments created through the REST API. It does not depend on the Initiate Shared Payments from Source setting, which is applied automatically while the AR setting is on. Set the Shared Payments Bank Account field on the invoice if the receiving subsidiary has more than one bank account and you want a specific one.
Apply each customer payment to one invoice
The journal is created automatically only when a customer payment is applied to exactly one invoice that has a Shared Payment Subsidiary. A payment applied to several of those invoices is not rerouted. To receive payment for several invoices, use the Customer Invoices tab of the Apply Payments screen, which creates the journals and the payments for you. See Shared Transactions - Shared Payments - Applying payments in batch.
An approved payment cannot be moved
If the customer payment is already approved when it saves, NetSuite does not allow its account to change, so Shared Payments cannot move it to the Shared Payment Subsidiary. Shared Payments records a message on the invoice that explains what was left behind.
Payments to Undeposited Funds are still rerouted
A customer payment entered to Undeposited Funds is still intercepted. Shared Payments moves it to the Shared Payment Subsidiary's bank account and marks it as deposited, so it does not appear on Make Deposits.
