Electronics retailers and distributors can process a large number of purchases through technology distribution partners such as Ingram.

Over the course of a month, the vendor account may contain much more than purchase invoices.

It can include:

• New invoices
• Payments
• Credit notes
• Debit notes
• Adjustments
• Older outstanding transactions

The retailer records these transactions in its SAP vendor ledger.

Ingram maintains its own account statement for the retailer.

Both records ultimately represent the same commercial relationship, but the two ledgers may not always agree transaction by transaction.

An invoice may exist in Ingram's statement but not yet be booked in SAP.

A payment may exist on both sides but be represented using different references.

A credit note may be present in one ledger and missing from the other.

The invoice reference may agree while the accounting value differs.

This creates a recurring reconciliation requirement:

SAP Vendor Ledger ↔ Ingram Vendor Statement

Cointab can automate this comparison and provide a transaction-level reconciliation showing which records agree, which records have value differences, and which entries exist on only one side.

The same workflow can then be repeated every month as new Ingram transactions are added and older open items are resolved.

---

Why Ingram vendor reconciliation can become complicated

At first glance, vendor reconciliation appears straightforward.

The retailer has one ledger.

The vendor has another ledger.

Compare the two and find the difference.

The difficulty is that a vendor account is not simply a list of invoices.

Over time, the account may contain several types of transactions that affect the balance:

Invoices → Payments → Credit Notes → Debit Notes → Adjustments

Each transaction may use a different reference.

In addition, SAP and Ingram structure their exports differently.

The reconciliation therefore needs to determine not only whether the final balances agree, but also:

• Whether the same invoices exist on both sides
• Whether the invoice amounts agree
• Whether credits have been recorded in both ledgers
• Whether debit notes are reflected correctly
• Whether payments can be identified
• Which transactions remain open
• Which side needs to take corrective action

For a high-volume electronics retailer, performing this analysis manually every month can result in substantial spreadsheet work.

---

What does the SAP vendor ledger contain?

A typical SAP ledger used for the Ingram vendor account may include:

This file contains several possible transaction identifiers.

The Ingram invoice number may be present in:

• Remarks
• Ref. 1
• Ref. 2
• Document-related fields
• Another available reference

The exact location can vary from one transaction to another.

This is one reason vendor reconciliation becomes difficult when it depends entirely on a single Excel lookup column.

---

What does the Ingram vendor statement contain?

The Ingram statement has a much more compact structure:

This layout is particularly useful because it exposes different types of commercial references directly.

For example:

• InvNum may identify an invoice.
• Chq/CN/DNNo may identify a cheque, credit note or debit note.
• Reference may contain additional information needed to connect the transaction with SAP.
• Debit and Credit represent the financial impact of the transaction.
• Cur identifies the currency.
• Cumulative Balance shows how each entry affects the running vendor balance.

The reconciliation therefore involves more than simply comparing invoice numbers.

It is a comparison of the full vendor-account movement.

---

Ingram reconciliation is really an open-item reconciliation

A useful way to think about this process is as an open-item reconciliation.

The objective is not only to prove that historical transactions once existed.

The objective is to identify which items still prevent the two ledgers from agreeing.

Suppose the account contains:

• 4,000 invoice transactions
• 300 payment entries
• 120 credit notes
• 25 debit notes

Most transactions may already be correctly reflected in both systems.

The finance team's attention should be concentrated on the relatively small population where:

• One side is missing the transaction
• The reference differs
• The amount differs
• The transaction was posted in a different period
• The transaction needs manual investigation

Cointab helps convert the complete ledger into this smaller exception population.

---

Why invoice matching alone is not sufficient

If a reconciliation looks only at InvNum, it may work for invoice transactions but provide an incomplete picture of the vendor account.

The Ingram statement can also include references through:

Chq/CN/DNNo

These may represent:

• Cheques or payments
• Credit notes
• Debit notes

These transactions can be critical when explaining why the SAP and Ingram balances differ.

For example, both systems may contain an invoice for:

₹5,00,000

but Ingram may also show a credit note of:

₹25,000

If that credit note has not been recorded in SAP, the invoice itself may appear correct while the overall vendor balance remains different.

A complete reconciliation therefore needs to consider the broader account movement.

---

How to reconcile SAP with Ingram using Cointab

Cointab provides a ready-to-use Vendor Reconciliation workflow.

The finance team does not need to redesign the process for every month.

The basic flow is:

Start Vendor Reconciliation → Upload SAP Ledger → Upload Ingram Statement → Configure Fields → Run Reconciliation

---

Step 1: Start a Vendor Reconciliation

Create a new reconciliation in Cointab.

Select:

Vendor Reconciliation

For this workflow:

• Company ledger = SAP
• Vendor statement = Ingram

The reconciliation can then be configured using the actual columns available in both files.

---

Step 2: Upload the SAP ledger

Upload the SAP export for the Ingram vendor account.

Cointab asks the user to map the relevant information.

Select the date

The SAP file provides:

• Posting Date
• Document Date

The appropriate date can be selected based on how the retailer performs the reconciliation.

Select transaction identifiers

Useful SAP fields may include:

• Doc. No.
• Trans. No.
• Remarks
• Ref. 1 (Header)
• Ref. 2 (Header)
• Ref. 1 (Row)
• Ref. 2 (Row)

Multiple relevant fields can be selected.

This is helpful because the underlying Ingram reference may not always be maintained in exactly the same SAP column.

Select the amount columns

Map:

• Debit (LC)
• Credit (LC)

Cointab can now interpret the financial values represented in the SAP vendor account.

---

Step 3: Upload the Ingram statement

Upload the corresponding Ingram ledger.

The configuration is different because the vendor file has its own structure.

Select the transaction date

The Ingram file contains:

Inv/CHQ Dt

This can be used as the relevant transaction date for the reconciliation.

Select transaction identifiers

Useful Ingram identifiers can include:

• InvNum
• Chq/CN/DNNo
• Reference

These fields may represent different transaction types and provide several ways to connect a record to SAP.

Configure debit and credit

Map:

• Debit
• Credit

The file also contains:

Cur

which provides the transaction currency where relevant.

Once the files are configured, the reconciliation can be started.

---

Cointab identifies references across both ledgers

One of the difficult parts of vendor reconciliation is that the transaction reference may not be written identically in both systems.

For example:

Ingram

InvNum: 48576392

SAP Remarks

ING INV 48576392

Or SAP may contain:

Ingram/48576392/Purchase

while Ingram contains only:

48576392

A strict character-for-character lookup can fail in such situations.

Cointab uses the configured identifier fields and AI-assisted identifier extraction to identify useful references from the ledger data.

The system can then use those identifiers while comparing transactions across both files.

---

Fully Matched Ingram transactions

An invoice can be classified as Fully Matched when:

1. The corresponding transaction can be identified in both SAP and Ingram.
2. The relevant amount agrees.

For example:

Ingram

Invoice:

48576392

Amount:

₹7,25,000

SAP

Reference:

48576392

Amount:

₹7,25,000

There is no financial difference.

The transaction is therefore:

Fully Matched

These transactions can generally be removed from the finance team's exception workload.

---

Partially Matched Ingram invoices

An invoice may exist in both ledgers while the amounts differ.

For example:

Ingram

Invoice:

48576392

Amount:

₹7,25,000

SAP

Invoice:

48576392

Amount:

₹7,10,000

The common invoice reference establishes the relationship.

However, the difference is:

₹15,000

Cointab classifies the transaction as:

Partially Matched

This immediately tells the finance user that the problem is not a missing invoice.

The problem is a financial difference within an identified transaction.

---

What can cause a partial match?

Possible causes include:

• Invoice entered at the wrong amount
• Missing credit note
• Missing debit note
• Incorrect adjustment
• Tax difference
• Incorrect SAP posting
• Vendor-side amount difference
• Transaction split differently across records

The finance team can investigate the supporting documents and determine which ledger needs to be corrected.

---

Transactions present in Ingram but not in SAP

Suppose the Ingram statement contains:

InvNum: 49281734

Amount:

₹10,80,000

but Cointab cannot find a corresponding SAP transaction.

The item appears under:

Present in Ingram but not in SAP

This category can be particularly useful for the internal accounts payable team.

Possible explanations include:

• Ingram invoice has not yet been booked
• Invoice was missed
• Invoice was booked using an incorrect reference
• Invoice was posted against the wrong vendor
• Transaction was posted in a later period
• Supporting document is still being processed

Instead of searching the entire vendor ledger, the team receives a specific list of transactions to investigate.

---

Transactions present in SAP but not in Ingram

The opposite scenario can also occur.

SAP may contain a transaction that does not appear in the Ingram statement.

For example:

SAP

Reference:

49326571

Amount:

₹4,60,000

Ingram

No corresponding transaction identified.

Cointab reports:

Present in SAP but not in Ingram

The retailer can investigate whether:

• SAP entry is incorrect
• Reference is different in Ingram
• Transaction belongs to another period
• Vendor has not yet accounted for the transaction
• Entry requires confirmation from Ingram

Relevant exceptions can then be shared with the vendor.

---

Reconciling Ingram credit notes

Credit notes are particularly important in distributor reconciliation.

A credit note may arise because of:

• Product return
• Pricing correction
• Commercial scheme
• Discount
• Short supply
• Damaged goods
• Other adjustment

The Ingram statement may identify such a transaction through:

Chq/CN/DNNo

Suppose Ingram records:

Credit Note: CN45872

Amount: ₹40,000

If SAP does not contain the corresponding credit, the vendor balance can remain different even though all major invoices match.

The reconciliation helps surface this as an unresolved transaction rather than leaving the team with an unexplained closing-balance difference.

---

Reconciling debit notes

Debit notes can create a similar issue.

The retailer may raise or record a debit adjustment related to:

• Pricing
• Returns
• Claims
• Short supply
• Commercial deductions
• Other vendor disputes

The transaction may exist in SAP under one reference while Ingram shows another reference in:

Chq/CN/DNNo

The finance team can use the reconciliation output to determine whether the corresponding debit adjustment has been recognized by both sides.

---

Reconciling payments and cheque references

The Ingram statement can also contain cheque or payment information.

A payment may be identified through:

Chq/CN/DNNo

with its date represented through:

Inv/CHQ Dt

SAP may contain the same payment using a different internal document or transaction number.

The finance team may therefore review combinations of:

• Payment amount
• Payment date
• SAP transaction reference
• Ingram cheque reference
• Other available reference information

This is useful when invoices reconcile correctly but payment allocation still causes a ledger difference.

---

One Ingram column can represent several document types

A distinctive feature of this statement is:

Chq/CN/DNNo

The field itself may carry references to different types of transactions.

For example:

• Cheque
• Credit note
• Debit note

The finance team therefore cannot always treat every non-invoice reference in exactly the same way.

The surrounding transaction information matters.

Useful context includes:

• Debit or credit side
• Date
• Reference
• Amount
• Related invoice
• Ledger description

Cointab allows multiple fields to be configured for identification so the reconciliation does not depend on one reference alone.

---

Using debit and credit direction to understand the account

Vendor statements can be confusing because the same commercial event may be represented differently depending on which party's accounting perspective is being viewed.

The SAP file contains:

• Debit (LC)
• Credit (LC)

The Ingram file contains:

• Debit
• Credit

During setup, the finance team maps the relevant debit and credit columns.

Cointab uses the configured account structure while comparing the transactions.

This reduces the need to manually create a new net-amount formula every time a revised ledger is received.

---

Currency information in the Ingram ledger

The Ingram statement also includes:

Cur

This can be useful where the vendor account contains or reports currency information alongside the transactions.

Currency provides another useful piece of context during reconciliation.

For example, two transactions should not be assumed to represent the same financial item purely because:

• Invoice number is similar
• Amount is identical

if the underlying currencies differ.

The available transaction fields can therefore be used together to build a more reliable reconciliation.

---

Why cumulative balance is useful but not enough

Both files contain a form of running balance:

SAP

Cumulative Balance (LC)

Ingram

Cumulative Balance

These balances are useful for confirming that a difference exists.

However, they do not explain the difference.

For example:

SAP Closing Balance: ₹6.92 crore

Ingram Closing Balance: ₹6.78 crore

Difference:

₹14 lakh

The real questions are:

• Which invoice is missing?
• Which credit note has not been recorded?
• Is a debit note pending?
• Has a payment been allocated differently?
• Is there an amount difference in an existing invoice?

Transaction-level reconciliation answers these questions.

---

Manual matching when the finance team knows the relationship

Some valid transactions may remain unmatched because their references are substantially different.

For example:

SAP

Remarks:

INGRAM ADJ AUG

Amount:

₹65,000

Ingram

Reference:

CN78452

Amount:

₹65,000

The finance user may know from supporting documents that these transactions represent the same credit adjustment.

Cointab provides a Manual Match option.

The user can:

1. Select the relevant SAP transaction.
2. Select the corresponding Ingram transaction.
3. Review the selected values.
4. Confirm the match.

The reconciliation then records the finance team's decision.

---

Manual Match is useful for historical open items

Vendor accounts often contain older transactions where references are not clean.

For example:

• Legacy postings
• Manually entered references
• Old credit notes
• Adjustments
• Rebooked entries
• Payments allocated using different descriptions

Cleaning all historical accounting data simply to make Excel formulas work may not be practical.

Manual Match allows users to resolve genuine transaction relationships while preserving the original source ledgers.

---

A practical monthly Ingram reconciliation workflow

Once the reconciliation is configured, the finance team's recurring process can be standardized.

A typical month may look like this:

1. Export the latest Ingram vendor ledger from SAP.
2. Obtain the latest account statement from Ingram.
3. Upload the SAP file into Cointab.
4. Configure the relevant date and identifier fields.
5. Map SAP debit and credit columns.
6. Upload the Ingram statement.
7. Map InvNum, Chq/CN/DNNo, Reference, date, debit and credit.
8. Run the reconciliation.
9. Review Fully Matched transactions.
10. Investigate Partially Matched invoices.
11. Review transactions present only in Ingram.
12. Review transactions present only in SAP.
13. Manually match valid exceptions where required.
14. Download the reconciliation working.
15. Send internal missing entries to the accounting team.
16. Share vendor-side exceptions with Ingram.
17. Correct the relevant ledgers.
18. Upload the revised data and reconcile again.

This converts a recurring spreadsheet exercise into a repeatable monthly process.

---

Example: an invoice exists in Ingram but has not been booked in SAP

Suppose Ingram shows:

Invoice: 50123874

Amount: ₹11,20,000

The transaction does not appear in SAP.

Cointab reports:

Present in Ingram but not in SAP

The accounts payable team reviews the invoice and confirms that it was not posted.

The transaction is subsequently booked in SAP.

When the updated SAP ledger is uploaded, Cointab can now compare:

SAP

50123874
₹11,20,000

Ingram

50123874
₹11,20,000

The transaction can move from an exception to:

Fully Matched

---

Example: a credit note is causing the vendor balance difference

Consider a situation where all major invoices appear to reconcile.

However, Ingram shows:

Credit Note: CN67291

Amount: ₹85,000

SAP does not contain the corresponding entry.

The total vendor balances therefore remain different by ₹85,000.

Instead of manually reviewing every invoice again, the reconciliation isolates the credit transaction that exists only in Ingram.

The finance team can investigate whether the credit note needs to be booked internally.

---

Example: invoice number matches but value does not

Suppose both systems contain:

Invoice: 50987651

But:

SAP

₹18,40,000

Ingram

₹18,55,000

The invoice is not treated as completely unrelated.

Cointab identifies the common invoice reference and categorizes the transaction as:

Partially Matched

The finance team can immediately investigate the ₹15,000 difference.

---

Example: payment references do not match

Suppose SAP contains a payment:

Amount: ₹25,00,000

SAP Reference: PAY-240781

Ingram shows:

Cheque No.: 784521

Amount: ₹25,00,000

The finance user knows that these represent the same payment.

If the records cannot be automatically linked with sufficient confidence, the user can select the corresponding transactions and complete a Manual Match.

This prevents genuine payments from remaining permanently open simply because the two companies use different reference numbers.

---

Previously unmatched items can reconcile in future periods

Not every difference represents an error.

Some are timing differences.

For example:

August reconciliation

Ingram records an invoice on 30 August.

The retailer has not yet posted it in SAP.

The invoice appears as:

Present in Ingram but not in SAP

September reconciliation

The AP team posts the invoice in SAP.

When the latest ledger is uploaded, the new SAP entry can reconcile against the previously open Ingram item.

The finance team therefore does not need to rebuild a separate spreadsheet of historical open transactions every month.

The reconciliation can continue as the underlying ledgers evolve.

---

Download the complete Ingram reconciliation in Excel

After reviewing the reconciliation, the finance team can download the complete working in Excel.

The output provides a structured record of the transaction-level reconciliation.

It can be used to review:

• Fully Matched transactions
• Partially Matched transactions
• SAP-only transactions
• Ingram-only transactions
• Manual Matches
• Relevant underlying ledger fields

This can serve as the finance team's prepared vendor reconciliation working for the period.

---

Use the output to drive corrective action

A reconciliation becomes useful when exceptions are resolved.

The output naturally creates two worklists.

Internal action list

Transactions present in Ingram but missing from SAP can be reviewed internally.

The team can determine whether:

• Invoice needs to be booked
• Credit note needs to be recorded
• Reference is incorrect
• Entry exists elsewhere
• Transaction belongs to another period

Vendor action list

Transactions present in SAP but not identifiable in Ingram can be shared with the vendor where required.

Ingram can investigate:

• Missing transaction
• Different reference
• Pending credit
• Payment allocation
• Other statement difference

This makes the reconciliation an actionable coordination tool between both finance teams.

---

Correct the ledgers and rerun the reconciliation

Once the differences have been investigated, either side may update its records.

For example:

• Missing SAP invoice is booked
• Ingram credit note is added internally
• Payment allocation is corrected
• Incorrect amount is changed
• Reference is updated
• Vendor posts a missing transaction

The finance team can upload the revised ledgers again.

Cointab reruns the reconciliation and updates the results based on the latest records.

The dashboard therefore represents the current state of the vendor account rather than a static one-time comparison.

---

Why this matters for electronics retailers

Large electronics retailers may purchase products from several major manufacturers and technology distributors.

Each vendor can generate a large recurring ledger.

The finance team may therefore be running separate monthly reconciliations for:

• Product manufacturers
• Mobile brands
• Consumer electronics companies
• IT distributors
• Accessory suppliers
• Other large vendors

The Ingram account can be particularly transaction-heavy because distribution relationships may involve substantial volumes of:

• Invoices
• Credit adjustments
• Debit notes
• Payments

Automating the reconciliation reduces the effort required to determine which small subset of these transactions actually needs attention.

---

Move from ledger matching to exception management

A spreadsheet-led process may require the finance team to:

• Export SAP
• Copy Ingram data into another workbook
• Normalize debit and credit values
• Clean invoice references
• Search cheque numbers
• Separate credit notes
• Separate debit notes
• Run lookups
• Compare amounts
• Carry open items forward
• Manually maintain reconciliation status

This work repeats every month.

Cointab changes the workflow to:

Upload SAP → Upload Ingram → Run Reconciliation → Review Exceptions → Resolve Open Items

The finance team's time is spent investigating differences rather than recreating the comparison.

---

Who is this reconciliation useful for?

This workflow is particularly relevant for businesses that:

• Use SAP
• Purchase regularly from Ingram
• Receive an Ingram vendor statement
• Have large monthly transaction volumes
• Need to reconcile invoices, payments, credit notes and debit notes
• Currently perform vendor reconciliation in Excel
• Carry unresolved vendor items across periods
• Need a prepared reconciliation working for month-end review

It is especially relevant to electronics retailers and technology distributors with high-volume vendor accounts.

---

How Cointab supports SAP vs Ingram reconciliation

Cointab's Vendor Reconciliation workflow can help finance teams:

• Upload the SAP vendor ledger
• Upload the Ingram account statement
• Map different date fields on each side
• Configure SAP Debit and Credit columns
• Configure Ingram Debit and Credit columns
• Use InvNum as an invoice identifier
• Use Chq/CN/DNNo for payment, credit-note and debit-note references
• Use additional reference fields for matching
• Extract identifiers from ledger descriptions
• Automatically identify corresponding transactions
• Separate Fully Matched records
• Identify invoices with amount differences
• Identify transactions present only in SAP
• Identify transactions present only in Ingram
• Manually match transactions where references differ
• Download the entire vendor reconciliation working in Excel
• Upload revised ledgers after corrections
• Carry open transactions into subsequent reconciliation periods

---

Automate SAP vs Ingram vendor reconciliation with Cointab

Reconciling Ingram should not require rebuilding a complex Excel workbook every month.

The underlying objective is straightforward:

Identify the same invoices, payments, credit notes and debit notes in both ledgers and isolate anything that does not agree.

Cointab converts this into a repeatable workflow:

SAP Vendor Ledger → Ingram Statement → Automated Reconciliation → Exception Review → Corrections → Updated Reconciliation

Fully matched transactions are separated from the worklist.

Amount differences are shown as partially matched.

Entries existing on only one side are clearly identified.

Transactions with inconsistent references can still be resolved using Manual Match.

Once corrections are made, updated ledgers can be uploaded and reconciled again.

If your electronics retail or distribution business uses SAP and currently reconciles its Ingram vendor statement manually in Excel, Cointab can help automate the process.

Try Cointab

For larger SAP ledgers, customized formats, or more complex vendor reconciliation requirements:

Book a Demo