You are here:
Adjustment Types for Payment and Expense Records
Accounting Subledger assists you with adjustments by separating source records from transaction journal records. If the source record is updated, we generate new transaction journal records accordingly.
| Available in: Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions with Accounting Subledger |
Sometimes funds arrive by chunks over long periods of time. Sometimes they're promised but don't come at all. And sometimes, we make simple errors such as inadvertently swapping two digits.
The integrity of accounting data is critical. Although ideally, this data remains permanent after it's created, it occasionally requires adjustments. We recommend these approaches for specific adjustment scenarios.
There is no Payment object in Salesforce. In the One-Object Model, payments are represented by the primary object. In all other models, payments are represented by the secondary object. See Object Models for Accounting Sets.
- Scheduled Payment Changes
If you use the four-object model for accrual accounting, we recommend that the total of the secondary object's amounts remain equal to or less than the primary object's amount. If you change either one, update the other to match. - Adjustments to Records Marked as Paid
If a record is marked as paid and later determined to be incorrect, an adjustment is in order. - Refunds
Refunds are like other paid transactions, except that you enter them as a negative amount, and mark them as paid. - Write-Off Payments
Write-offs are standard in accrual accounting, which recognizes gift revenue when the gift is committed. Completing a write-off maintains the promised revenue amount, while acknowledging that it won't become available. - Differences Between Write-Offs and Refunds
Write-offs are for pledged amounts that you haven't received yet, and refunds are for completed payments that you want to reverse and return to the donor. - Negative Payment or Expense Amounts (Reversals)
Because you can't easily delete transaction journal records, Accounting Subledger uses negative payment or expense amounts to process refunds and reversals.
Scheduled Payment Changes
If you use the four-object model for accrual accounting, we recommend that the total of the secondary object's amounts remain equal to or less than the primary object's amount. If you change either one, update the other to match.
If the sum of the secondary object's amounts exceeds the primary object's amount, Accounting Subledger generates transaction journal records only up to the primary object's amount.
Adjustments to Records Marked as Paid
If a record is marked as paid and later determined to be incorrect, an adjustment is in order.
While you can change records at any time (for example, to correct errors made during entry), we recommend that you only do so when necessary. Before making any changes, confirm with your accounting teams that adjustments are allowed.
Transaction journal records are immutable, so, to make a correction, Accounting Subledger creates adjustment transaction journal records.
Amount Corrections
If there's a mistake in the payment amount, edit the record and then save your changes. For amount increases, decreases, or adjustments, we create delta amounts to account for the difference. For significant changes, such as a change to payment dates or funds, or if a payment is refunded, we reverse the record, and then create another record with the revised values.
If you’re using a three- or four-object accounting set, it can allow multiple fund account allocations, each with their own amount. When you change the related parent amount, we don’t automatically update allocations. Therefore, review each child amount and adjust them as needed so that they add up to the parent amount.
- The total amount of allocation type records under a parent record must equal the same amount as the parent record.
- In a four-object model, the sum of the secondary object payment or expense type records' amounts must equal the overall amount on the primary object's record.
Refunds
Refunds are like other paid transactions, except that you enter them as a negative amount, and mark them as paid.
Choose the allocations that the refund comes from and whether it's part of an existing set of records. For example, a refund, full or partial, can apply to a multiple-payment gift or to an entire payment.
To reverse a record that's marked as paid, generate a refund by creating another record with a negative amount.
- Create a new payment or expense record.
- Enter the refund Amount as a negative number. For example, enter -200 for a US$200 refund.
- Select Payment is Paid.
- Enter the date on which the refund was processed in Payment Paid Date.
- Enter the method that was used to issue the refund in Payment Method.
- Save your changes.
Refunds generate the same transaction journal records as regular payments and expenses. Therefore, if the record still exists with the original amount, Salesforce also creates a debit entry in the receivables account. To avoid that, reduce the amount on the source record by the refund amount after you created the refund payment. For example, you have an opportunity amount of $100, and a donor makes a $100 donation. They later want a refund on the donation that you already marked as paid. If you create a $100 refund on the opportunity, also reduce the opportunity amount to $0 so that we don't create an entry in the receivables account.
If applicable, you can also write off a payment so that the original payment is reversed.
Write-Off Payments
Write-offs are standard in accrual accounting, which recognizes gift revenue when the gift is committed. Completing a write-off maintains the promised revenue amount, while acknowledging that it won't become available.
Occasionally you receive notice that a donor can't fulfill their pledge and won't send a payment. To write off a payment, follow the same steps for receiving a payment, except select Written Off instead of Paid on the source record. You don't have to set a payment method.
Accounting Subledger generates transaction journal records after a write-off just as it would for a payment that's marked as paid. However, the transaction and payment types of transaction journal records are marked as written off, indicating that the revenue wasn't received.
Differences Between Write-Offs and Refunds
Write-offs are for pledged amounts that you haven't received yet, and refunds are for completed payments that you want to reverse and return to the donor.
You can use refunds to enter negative payments that aren’t associated with a specific donation. For example, create a refund for a payment processed in a different period, or to track a payment that wasn’t initially entered in Salesforce.
Accounting Subledger creates transaction journal records differently depending on which adjustment you make.
| Type of Adjustment | Number of Transaction Journal Records Created | Type of Transaction Journal Record Created | Account Where Transaction Journal Records Are Created |
|---|---|---|---|
| Write-off | Two* | Credit | Default Accrued Account Code |
| Debit | Default Write Off Account Code | ||
| Refund | Four | Credit for the initial payment | Payment Method |
| Debit for the initial payment | Fund Name | ||
| Credit for the refunded payment | Payment Method | ||
| Debit for the refunded payment | Default Accrued Account Code |
* If you already received payments and only want to write off some of them, Accounting Subledger still creates transaction journal records for those payments like it does for refunds.
Negative Payment or Expense Amounts (Reversals)
Because you can't easily delete transaction journal records, Accounting Subledger uses negative payment or expense amounts to process refunds and reversals.
The debit and credit amounts are reversed. For example, Salesforce posts debits in the original fund and credits in the cash fund. See Accounting Subledger Terminology.
You can use negative payments to refund a record that wasn't initially entered in Salesforce, even if it exceeds the original amount on the source record.
For example, you enter a record for US$100 cash to be directed to your general fund. When you run Accounting Subledger, it generates a debit transaction journal record of $100 in the cash account and a $100 credit transaction journal record in the general fund.
The next day, a team member deletes the record after realizing that the $100 payment was meant for another department that uses a different system. We don't delete the generated transaction journal records, and you now likely want to reverse them.
To create reversals and cancel the original transaction before the team member deleted the primary object record:
- Change the amounts on the primary and related object records to $0.
This change directs Accounting Subledger to create reversal records for any existing transaction journal records.
- Wait until the Accounting Subledger job runs.
- Verify that the job created reversal transaction journal records accurately.
- Delete the primary object record and any related records.

