Large electronics retailers can purchase substantial volumes of televisions, appliances, air conditioners, monitors, and other products from LG throughout the year.

Every invoice, payment, debit note, credit, and adjustment relating to those purchases should eventually be reflected in two places:

1. The retailer's LG vendor account in SAP
2. The account statement maintained and shared by LG

In theory, both ledgers should arrive at the same position.

In practice, differences are common.

An LG invoice may appear in the vendor statement before the retailer has booked it in SAP.

A payment may exist in SAP but appear under a different cheque or reference number in LG's statement.

An invoice number may be present on both sides while the amount recorded is different.

Some older transactions may remain outstanding for several accounting periods simply because nobody has identified exactly which entry is causing the difference.

This is why finance teams periodically perform:

SAP Vendor Ledger ↔ LG Vendor Statement Reconciliation

Cointab can automate this comparison and turn two differently structured ledger exports into a transaction-level vendor reconciliation showing what agrees, what differs, and which side needs to take action.

---

What is SAP vs LG vendor reconciliation?

The purpose of the reconciliation is to compare every relevant LG transaction recorded by the retailer against the corresponding transaction recorded by LG.

The finance team wants to establish:

• Which invoices exist in both ledgers
• Whether matching invoices have the same amount
• Which transactions exist only in SAP
• Which transactions exist only in LG's statement
• Whether payments and cheque references can be connected
• Which transactions require manual investigation

Instead of simply comparing the closing balances, the reconciliation explains the transactions responsible for any difference.

The output can broadly be classified into:

• Fully Matched
• Partially Matched
• Present in SAP but not found in LG
• Present in LG but not found in SAP
• Manually Matched

---

Understanding the SAP LG vendor ledger

An SAP vendor ledger used by an electronics retailer can contain fields such as:

The SAP file contains rich accounting information, but the actual LG invoice number may not always be stored in one consistent field.

For example, the invoice number could be present in:

• Ref. 1
• Ref. 2
• Remarks
• Document reference
• Another transaction-level field

This is one reason an automated reconciliation should be able to work with several possible identifiers instead of depending on a single invoice column.

---

Understanding the LG vendor statement

The LG ledger has a different structure.

A typical LG vendor statement may contain:

This format provides several useful clues during reconciliation.

Invoice transactions can potentially be identified through:

• Invoice No.
• Reference
• Remarks

Payment transactions may also contain useful information in:

• Cheque No.
• Cheque Date
• Reference

The challenge is connecting these fields to the references used inside SAP.

---

Why the SAP and LG files cannot simply be compared column by column

The SAP and LG files represent the same vendor relationship, but they have been generated by two completely different accounting environments.

For example:

SAP may identify a transaction using:

Ref. 1 (Header)

while LG may identify the same transaction using:

Invoice No.

A payment may appear in SAP through a transaction reference while LG identifies it through:

Cheque No.

Dates may also differ.

SAP may use:

Posting Date

while LG shows:

GL Date

The actual invoice may additionally have:

Document Date

and:

Inv. Date

All of these dates can legitimately differ.

The files therefore need to be reconciled based on the economic transaction rather than assuming the same columns exist on both sides.

---

How electronics retailers can reconcile SAP with LG in Cointab

Cointab includes a standard Vendor Reconciliation workflow.

The finance team can configure the LG reconciliation without first converting both files into one common Excel template.

The process broadly involves:

Create Vendor Reconciliation → Upload SAP Ledger → Upload LG Statement → Configure Fields → Run Reconciliation

---

Step 1: Create a Vendor Reconciliation

Start a new reconciliation in Cointab and select:

Vendor Reconciliation

This establishes the basic workflow for comparing the company's vendor ledger with the statement received from the supplier.

For this use case:

• Internal ledger = SAP
• Vendor ledger = LG

---

Step 2: Configure the SAP ledger

Upload the SAP export for the LG vendor account.

Cointab asks the user to configure the relevant transaction fields.

Date

Select the date appropriate for the reconciliation.

Depending on the retailer's accounting process, this could be:

• Posting Date
• Document Date

Identifiers

Select the SAP fields that can help identify LG transactions.

Possible fields include:

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

Rather than assuming the invoice number always exists in one field, multiple relevant identifier columns can be used.

Amount columns

Configure:

• Debit (LC)
• Credit (LC)

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

---

Step 3: Configure the LG statement

Upload the statement received from LG.

Configure the fields relevant to the reconciliation.

Date

The LG statement provides fields such as:

• GL Date
• Inv. Date
• Cheque Date

For invoice reconciliation, the appropriate transaction date can be selected based on the reconciliation process.

Identifiers

Useful LG reference fields can include:

• Invoice No.
• Cheque No.
• Reference
• Remarks

These fields help Cointab identify the transaction represented by each row.

Amount columns

Configure:

• DR
• CR

Once the two files have been mapped, the reconciliation can be started.

---

Cointab extracts transaction identifiers from the ledgers

Vendor ledger references are rarely perfectly standardized.

Consider these entries:

SAP

LG INV 4500087654

LG

4500087654

Or SAP may contain the number inside a longer remark:

Purchase LG Invoice 4500087654 BLR

while LG simply records:

4500087654

Finance teams working in Excel may need to clean these descriptions, split strings, create helper columns, or manually search for invoice numbers.

Cointab uses AI-assisted processing to identify useful references contained across the configured identifier fields.

This helps the reconciliation work even when the relevant invoice number is embedded inside a larger ledger description.

---

What does a Fully Matched LG invoice mean?

A transaction is Fully Matched when Cointab identifies the corresponding invoice in both ledgers and the financial values agree.

For example:

SAP vendor ledger

Invoice: 4500087654

Amount: ₹8,40,000

LG vendor statement

Invoice: 4500087654

Amount: ₹8,40,000

There is:

• A corresponding invoice on both sides
• No amount difference

The transaction can therefore be classified as:

Fully Matched

For the finance team, this means the invoice does not require further investigation as part of the reconciliation.

---

What does a Partially Matched invoice mean?

An invoice may be clearly identifiable in both SAP and LG but contain different amounts.

For example:

SAP

Invoice: 4500087654

Amount: ₹8,40,000

LG

Invoice: 4500087654

Amount: ₹8,55,000

The invoice number confirms that the two entries relate to the same transaction.

However, the values differ by:

₹15,000

Cointab therefore reports the transaction as:

Partially Matched

Instead of losing this transaction among the unmatched population, the finance team immediately knows that the issue is an amount difference, not a missing invoice.

---

What can cause an amount difference?

A partially matched LG transaction may require investigation for reasons such as:

• Invoice booked at the wrong value
• Debit note missing
• Credit note missing
• Discount treated differently
• Tax difference
• Adjustment present on only one side
• Incorrect posting in SAP
• Incorrect value in the vendor statement

Once the cause is understood and the appropriate accounting entry is corrected, updated ledgers can be reconciled again.

---

Entries present in LG but missing from SAP

One of the most useful outcomes of an LG vendor reconciliation is identifying transactions that LG has recorded but the retailer has not.

For example:

LG statement

Invoice No.: 4500098765

Amount: ₹12,75,000

SAP

No corresponding invoice found.

Cointab reports this transaction under:

Present in LG but not present in SAP

This exception is especially actionable for the retailer's accounts payable team.

Possible causes include:

• Invoice has not yet been booked
• Invoice was overlooked
• Invoice was booked under an incorrect reference
• Invoice was posted against another vendor account
• Transaction belongs to a later SAP posting period
• Accounting entry is still pending

The reconciliation output can be shared internally for investigation.

---

Entries present in SAP but missing from LG

The reverse situation can also occur.

For example:

SAP

Reference: 4500074321

Amount: ₹6,30,000

LG

No corresponding transaction found.

The transaction is classified as:

Present in SAP but not present in LG

Possible causes can include:

• Incorrect SAP entry
• Incorrect vendor posting
• Different LG reference
• Timing difference
• Vendor-side entry still pending
• Adjustment recorded differently

These items can be shared with the LG finance team where vendor confirmation is required.

---

Using LG cheque numbers during reconciliation

LG's statement includes fields such as:

• Cheque No.
• Cheque Date

These can provide useful information when reconciling payment-related transactions.

The original invoice reconciliation may rely primarily on invoice references, but payment exceptions can require another layer of investigation.

For example, a retailer may see a payment in SAP while LG identifies the same payment through its cheque number or another reference.

The finance team can use these supporting identifiers when reviewing transactions that did not reconcile automatically.

This makes the LG statement particularly useful for investigating:

• Payment allocation differences
• Cheques appearing against different invoices
• Payments posted in different periods
• References that differ from SAP

---

GL Date versus SAP Posting Date

Another important distinction is transaction timing.

LG may use:

GL Date

while SAP contains:

Posting Date

and:

Document Date

These do not necessarily need to be identical.

For example:

LG invoice date:

29 July

LG GL Date:

30 July

SAP document date:

29 July

SAP posting date:

2 August

The transaction is still potentially the same invoice.

A reconciliation based only on exact dates could incorrectly classify such records as different.

Cointab allows the reconciliation configuration to use the appropriate dates together with identifiers and financial values.

---

Manual Match for known LG transactions

There will always be some exceptions where the data alone does not establish the relationship with sufficient confidence.

Suppose:

SAP

Reference:

LG-INV-987654

Amount:

₹4,90,000

LG

Invoice No.:

987654

Amount:

₹4,90,000

The finance user understands the transaction and confirms that these are the same invoice.

Cointab's Manual Match workflow allows the user to:

1. Select the SAP transaction.
2. Select the corresponding LG transaction.
3. Review the selected records.
4. Confirm the manual match.

The reconciliation then records the relationship accordingly.

---

Manual matching preserves finance-team judgment

Vendor reconciliation cannot always be solved purely through formulas.

Finance users may know information that is not explicitly represented in either file.

For example:

• An LG reference was entered incorrectly in SAP.
• An old invoice was rebooked.
• Two entries use different numbering conventions.
• A payment was applied differently.
• The same transaction has different descriptions in both ledgers.

Manual matching allows this business knowledge to be incorporated into the reconciliation without manipulating source data simply to force a formula to work.

---

From closing balance difference to transaction-level explanation

Many vendor reconciliations begin with two different closing balances.

For example:

SAP LG Vendor Balance: ₹12.64 crore

LG Statement Balance: ₹12.51 crore

Difference: ₹13 lakh

The ₹13 lakh tells the team that something is wrong.

It does not tell them what is wrong.

A transaction-level reconciliation breaks the difference into actionable categories:

• Fully Matched invoices
• Invoices with amount differences
• Transactions only in SAP
• Transactions only in LG
• Transactions manually linked by the finance team

This makes the balance difference explainable rather than simply observable.

---

Download the LG reconciliation working in Excel

Once the review is complete, the entire reconciliation can be downloaded from Cointab.

The Excel working contains the transaction-level output used during the reconciliation.

Finance teams can use it for:

• Month-end working papers
• Internal AP follow-up
• Vendor discussions
• Exception tracking
• Audit support
• Subsequent reconciliation

Instead of maintaining several versions of an Excel reconciliation with changing formulas and manual markings, the downloaded file reflects the structured reconciliation performed in Cointab.

---

What should the retailer do with LG-only transactions?

Transactions appearing in LG but not in SAP typically require an internal review.

The finance team can share the relevant exceptions with:

• Accounts payable
• Purchase accounting
• Relevant branch or business team
• Other internal stakeholders

The team can determine whether:

• The invoice should be booked
• The invoice is already recorded using another reference
• The transaction is incorrect
• The transaction belongs to another period

If an entry was genuinely missed, it can be recorded in SAP.

---

What should happen with SAP-only transactions?

Transactions appearing in SAP but not in LG may require discussion with the vendor.

The retailer can provide LG with the relevant exception details and supporting documentation.

LG can then investigate whether:

• The transaction is missing
• A different reference was used
• A credit or adjustment needs to be recorded
• The transaction belongs to another statement period

This makes the reconciliation a collaborative process between the retailer's finance team and LG rather than simply an internal balance comparison.

---

Reconcile the corrected ledgers again

After both parties investigate their respective exceptions, the underlying ledgers can change.

For example:

• Retailer books a missing LG invoice in SAP
• LG posts a missing credit
• SAP reference is corrected
• Amount is adjusted
• Old transaction is cleared

The finance team can upload the updated files again.

Cointab runs the reconciliation on the latest information and updates the reconciliation result.

An item that previously appeared as:

LG Only

may now become:

Fully Matched

An item previously classified as:

Partially Matched

may become fully reconciled once the amount difference has been corrected.

---

Example: an LG invoice is missing in SAP

Consider an LG invoice:

5100234567

Value:

₹9,80,000

LG's statement includes the invoice during the July reconciliation.

SAP does not contain it.

The transaction appears as:

Present in LG but not present in SAP

The finance team investigates and determines that the invoice was missed during posting.

The accounts payable team books the invoice in SAP.

When the revised SAP ledger is uploaded, Cointab can compare the new entry with LG's statement.

If the reference and amount now agree, the transaction moves to:

Fully Matched

The reconciliation therefore tracks the practical resolution of the exception.

---

Example: SAP and LG contain the same invoice but different values

Assume both ledgers contain:

Invoice 5100876543

SAP amount:

₹15,25,000

LG amount:

₹15,00,000

Because the invoice can be identified on both sides, Cointab does not treat it as two unrelated unmatched records.

It is classified as:

Partially Matched

The finance team immediately knows to investigate the ₹25,000 difference.

Once the correct value is established and the relevant ledger is updated, the revised data can be uploaded for another reconciliation run.

---

Example: the invoice number is formatted differently

Suppose the SAP remarks contain:

LGINV 5100123456

while the LG statement contains:

5100123456

Both transactions have the same amount.

The underlying identifier is present, but the source systems represent it differently.

Cointab can use the configured identifier fields and AI-assisted extraction to identify transaction references from ledger text.

Where an automatic match is still not appropriate, the finance user can complete the relationship through Manual Match.

---

Running the LG vendor reconciliation every month

LG reconciliation is typically a recurring accounts payable control rather than a one-time exercise.

Each month introduces new:

• Invoices
• Payments
• Adjustments
• Credit notes
• Debit notes
• Outstanding items

At the same time, differences from previous months may get resolved.

The monthly process can therefore become:

1. Export the latest LG vendor ledger from SAP.
2. Obtain the latest statement from LG.
3. Upload the SAP file to Cointab.
4. Upload the LG file.
5. Run Vendor Reconciliation.
6. Review Fully Matched invoices.
7. Investigate Partially Matched invoices.
8. Review LG transactions missing from SAP.
9. Review SAP transactions missing from LG.
10. Complete any required Manual Matches.
11. Download the reconciliation working.
12. Send internal exceptions to the accounts team.
13. Share vendor-side differences with LG.
14. Upload corrected ledgers when available.

The same reconciliation structure can then continue into the next period.

---

Previously open items can reconcile in a later month

A vendor reconciliation should not assume that every valid transaction must appear in both ledgers during exactly the same month.

Timing differences are common.

For example:

July

LG records an invoice.

SAP has not yet posted it.

The invoice remains unmatched.

August

The retailer records the invoice in SAP.

The next reconciliation contains the corresponding entry.

Cointab can now reconcile the previously outstanding transaction against the newly available SAP record.

This allows finance teams to carry genuine open items forward rather than manually rebuilding the history every month.

---

Why electronics retailers can benefit from automated LG reconciliation

Electronics retail businesses can have particularly large vendor ledgers because major brands supply many:

• Products
• Models
• Stores
• Warehouses
• Purchase orders
• Invoices
• Credit adjustments

If the LG ledger contains thousands of transactions, most may already agree with SAP.

The finance team's attention should therefore be directed toward the relatively small number of transactions where:

• An invoice is missing
• An amount differs
• A reference cannot be identified
• A payment remains unallocated

Automated reconciliation converts the process from bulk transaction checking into exception management.

---

Replace repetitive Excel work with a reusable reconciliation

A spreadsheet-led LG reconciliation may require users to repeatedly:

• Copy ledger exports
• Normalize debit and credit columns
• Clean invoice numbers
• Create helper columns
• Run lookups
• Compare amounts
• Mark exceptions
• Maintain previous-period open items
• Update formulas when new data arrives

Cointab converts the workflow into:

Upload SAP + Upload LG + Run Reconciliation + Review Exceptions

The finance team can concentrate on resolving accounting differences rather than rebuilding the matching exercise every month.

---

SAP vs LG reconciliation for electronics retailers

This reconciliation workflow is particularly relevant for electronics retailers and distributors that:

• Purchase products from LG
• Use SAP for accounting
• Maintain a dedicated LG vendor ledger
• Receive periodic LG account statements
• Process large numbers of LG invoices
• Perform monthly vendor reconciliation
• Currently reconcile the two ledgers in Excel
• Need transaction-level visibility into outstanding differences

The workflow can be configured around the actual SAP and LG ledger formats used by the business.

---

How Cointab supports SAP vs LG vendor reconciliation

Cointab's Vendor Reconciliation workflow allows finance teams to:

• Upload the SAP LG vendor ledger
• Upload the LG vendor statement
• Map date fields independently on both sides
• Configure SAP debit and credit columns
• Configure LG DR and CR columns
• Select multiple invoice and transaction identifier fields
• Extract useful references from ledger descriptions
• Automatically identify matching invoices
• Compare amounts for matched invoices
• Separate Fully Matched transactions
• Identify Partially Matched invoices
• Identify transactions available only in SAP
• Identify transactions available only in LG
• Manually match valid transactions with different references
• Download the final working in Excel
• Upload corrected ledgers and rerun the reconciliation
• Repeat the process for subsequent accounting periods

---

Automate SAP vs LG vendor reconciliation with Cointab

A monthly LG vendor reconciliation should help the finance team identify and resolve ledger differences.

It should not require hours of rebuilding Excel formulas every time a new statement arrives.

Cointab turns the process into a repeatable workflow:

SAP Vendor Ledger → LG Vendor Statement → Automated Matching → Exception Review → Corrections → Updated Reconciliation

The finance team receives a clear view of which LG transactions agree with SAP and which records require action from either the retailer or the vendor.

Once corrections have been made, revised ledgers can be uploaded and reconciled again.

If your electronics retail business uses SAP and currently reconciles its LG vendor statement manually, Cointab can help automate the monthly reconciliation.

Try Cointab

For custom SAP exports, large vendor ledgers, or more complex reconciliation requirements:

Book a Demo