---
schema_version: "1"
id: fef0889eae0f18a6e68b8720903f81da51260fa59c5e01fa669999df824751d6
title: Considerations for Gift Processing Education
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sfdo/264-0-0/ec_fundraising_considerations_for_gift_processing.md
canonical_url: https://help.salesforce.com/s/articleView?id=sfdo.ec_fundraising_considerations_for_gift_processing.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 17ea75c2a68ff59e630d6efad0234600081ae685476d469970dc7c85c206b977
description: Gift entries that aren't part of a gift batch are processed when you save them. For gift batches, complete a batch dry run and then explicitly process the gift entries in the batch.
products:
  - Education Cloud
release: "264"
---
# Considerations for Gift Processing Education

Gift entries that aren't part of a gift batch are processed when you save them. For gift batches, complete a batch dry run and then explicitly process the gift entries in the batch.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
      <colgroup>
        <col style="width:100%">
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d124278e36">REQUIRED EDITIONS</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="REQUIRED EDITIONS" class="slds-cell-wrap" style="vertical-align:top;" headers="d124278e36 ">Available in: Lightning Experience</td>

        </tr>
        <tr class="">
          <td data-label="REQUIRED EDITIONS" class="slds-cell-wrap" style="vertical-align:top;" headers="d124278e36 ">
            <p style="margin-bottom:0;">Available in: <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>,
              and <strong>Developer</strong> Editions with Education Cloud</p>
          </td>

        </tr>
      </tbody>
    </table>

It's not uncommon to add gifts to batch over a period of time. You might enter some of the gifts today and finish entering them at the end of the week. And in between, the data in Fundraising might change. Tracking these changes manually is cumbersome. To help prevent errors from occurring when you process your batch, initiate a batch dry run.

Batch dry runs simulate batch processing, validating the data and giving you the opportunity to correct errors. However, they don't commit anything in the database or create any records. You can address the errors and then actually process your batch.

For example, the dry run alerts you that the total count of gift entries in the batch doesn't match the estimated count of gift entries. You can review the gift batch and check for any missing entries, or correct the estimated count, or skip this check altogether, and then proceed with the actual processing of the batch.

During a batch dry run, you can't add or edit gift entries. After the dry run is complete, you can add, edit, or process gift entries.

You can process up to 50,000 gift entries at a time in a gift batch. When you process a gift batch, these records are created or updated for each gift entry in the batch:

- Gift transactions
- Gift transaction designations. If a gift entry is allocated to multiple designations, then the gift is split and multiple gift transaction designation records are created according to the allocation percentage and the amount specified in the gift entry.
- Gift soft credits. If a gift entry has multiple soft credit recipients, then multiple gift soft credit records are created per gift transaction.
- Accounts for new donors