A regional business may have impressive performance figures in its sales platform, finance software, branch reports and partner databases. The difficulty begins when those figures are combined. A transaction recorded by a retail outlet may also appear in the payment gateway, central reporting system and accounting ledger. Adding every reported total together could count the same transaction several times.

For a company preparing an Asia Record application, this creates an important question: how can several data sources be combined into one achievement figure that is accurate, understandable and capable of being checked?

The answer is not simply to select the largest number or produce a polished spreadsheet. It requires a clearly defined measurement, reliable source records, consistent inclusion rules and a transparent explanation of how duplicates were handled.

Why Multi-System Data Creates Problems for Record Claims

Many organisations do not operate from a single database. A retail group may have separate point-of-sale systems across its branches. A digital platform may collect activity through mobile applications, websites and third-party integrations. A manufacturer may maintain production records in factory systems, warehouse software and enterprise reporting platforms.

These systems often describe different stages of the same activity.

Consider an online purchase. The ordering platform records an order, the payment provider records a successful payment, the warehouse records fulfilment and the finance system records the resulting sale. All four entries may relate to one underlying commercial transaction.

Whether any particular entry should be counted depends on the proposed achievement. If the claim concerns completed customer purchases, counting the payment and warehouse entries as additional purchases would be misleading. If the claim concerns warehouse dispatches, the appropriate measurement could be different.

This distinction matters because Asia Record’s official verification approach evaluates a clearly defined claim against supporting evidence and the conditions required to measure it consistently. Applicants can review the official Asia Record verification process before preparing their supporting records.

Start by Defining Exactly What Is Being Counted

Before merging files, write a measurement definition that someone outside the organisation could understand.

For example, the phrase “total transactions” may refer to orders created, payments attempted, payments completed, invoices issued or purchases successfully fulfilled. Those measures are not interchangeable.

A useful measurement definition should answer:

• Unit: Is the claim counting transactions, customers, products, deliveries, participants or another defined unit?
• Qualifying event: What must happen before an entry becomes eligible for inclusion?
• Scope: Which businesses, branches, countries, platforms or partners are included?
• Period: What are the exact start and end dates, and which time zone applies?
• Exclusions: How are cancellations, reversals, tests, incomplete entries and duplicated records treated?
• Source: Which original records establish that each qualifying event occurred?

These questions are part of a practical editorial checklist for preparing consistent evidence. They are not a substitute for the conditions agreed with Asia Record for a specific proposed record.

Build a Source Inventory Before Combining Any Files

One of the most useful steps is to create a register of every system contributing information to the proposed achievement.

This prevents a common error: treating every system as an independent source of additional activity when some systems merely reproduce data collected elsewhere.

Data source	Information captured	Possible overlap	Recommended review
Point-of-sale system	Branch transactions	Central sales reporting	Identify original transaction IDs
Payment gateway	Payment attempts and outcomes	Point-of-sale and online orders	Match payments to qualifying transactions
Accounting software	Invoices and financial postings	Sales and payment systems	Use for reconciliation, not automatic additional counting
Partner database	Activity reported by partners	Central platform records	Confirm ownership and overlap
Management dashboard	Aggregated performance figures	Potentially all underlying systems	Trace totals to original records

The table illustrates typical business systems. It does not prescribe which evidence Asia Record will accept for every application.

For each source, document the system owner, reporting period, extraction date, file format, record count and relevant limitations. Retain the original export alongside any cleaned or consolidated version.

Choose an Authoritative Source for Each Measurement

Different systems can be authoritative for different questions.

A payment processor may provide strong evidence that a payment was completed. A warehouse system may establish when a shipment was dispatched. A customer database may help identify unique registered accounts.

None of these systems should automatically be treated as authoritative for every measurement.

The correct source depends on the unit being counted and the event that qualifies it for inclusion.

Where two systems record the same event, use a documented matching relationship rather than counting both entries independently. If an authoritative source cannot be identified, record the limitation and investigate it before relying on the total.

Use Unique Identifiers to Detect Duplicate Records

A unique identifier is a value intended to distinguish one transaction, customer, event or other unit from another.

Examples include an order ID, invoice reference, shipment number, event registration ID or internal transaction key.

Identifiers are particularly valuable when multiple systems share a reference to the same underlying event. However, an identifier is useful only if its meaning and reliability are understood.

An order number may be unique within one branch but reused by another branch. A customer may have separate account IDs across two applications. A payment may have a different reference from the order it settles.

Therefore, a matching rule may need several fields rather than one.

Example: A Composite Transaction Key

Suppose two branches use the same local invoice numbering sequence. Invoice 1058 at Branch A is not necessarily the same transaction as Invoice 1058 at Branch B.

A more useful matching key could combine the branch identifier, invoice identifier and relevant transaction date. Even then, the organisation must test whether the combination reliably identifies one qualifying transaction.

When identifiers are missing or inconsistent, supporting fields may help identify possible matches. Those matches should be reviewed rather than automatically treated as certain.

Distinguish True Duplicates From Legitimate Repeated Activity

Two records with similar information are not necessarily duplicates.

A customer may legitimately make two purchases of the same amount on the same day. A manufacturer may produce two batches of identical quantity. An event participant may register for two distinct activities.

Removing one of those records merely because the values look similar could understate the achievement.

Conversely, two records with different reference numbers may still describe the same underlying activity if one system generates a new identifier when information is transferred.

A reliable duplicate review therefore distinguishes three situations:

• Confirmed duplicate: Multiple entries represent the same qualifying unit and should contribute only once to a unique-unit total.
• Confirmed distinct record: Similar entries represent separate qualifying units and should remain included.
• Unresolved possible duplicate: Available evidence is insufficient to determine whether the entries represent one or several qualifying units.

Unresolved cases should not be silently classified in whichever way produces the most favourable result.

A Worked Example: Combining Three Business Systems

Consider a hypothetical retail group preparing a claim based on completed transactions across several operating channels.

The group exports transaction records from three systems. After aligning the measurement definition and reviewing matching identifiers, the team identifies overlap between the datasets.

Reconciliation item	Illustrative records
System A records	12,000
System B records	8,000
System C records	5,000
Combined raw records	25,000
Confirmed additional duplicate entries	3,200
Cancelled or otherwise ineligible entries not already excluded	800
Reconciled qualifying records	21,000

This is a hypothetical calculation, not an actual Asia Record achievement. It assumes that the duplicate and ineligible groups do not overlap, that every remaining record meets the measurement definition, and that no unresolved records affect the result.

The important lesson is not the size of the final number. It is the ability to explain how the figure was derived.

The team should be able to identify which source records contributed to the 21,000 qualifying entries, which records were excluded and why, and which matching rules were used.

If a reviewer questions one entry, the organisation should be able to trace it back to the relevant original source without reconstructing the entire calculation.

Standardise Data Without Changing Its Meaning

When datasets originate from several countries or platforms, they may use different conventions.

Dates may appear in different formats. Systems may store local timestamps or coordinated universal time. Branch names may have different spellings. Financial values may be reported in different currencies. Product categories may follow different classification systems.

Standardisation makes records comparable, but it must not conceal meaningful differences.

For example, converting timestamps into a common time zone can help determine whether transactions fall within the stated measurement period. The original timestamps and their time-zone context should remain available.

Similarly, changing branch labels into a common naming convention should not merge legally or operationally distinct locations without justification.

Where currency conversion is relevant, the conversion method, source rates and applicable dates should be documented. A converted financial total should not be presented as an original system value.

Preserve the distinction between original observations and derived calculations.

Keep a Reconciliation Log That Explains Every Adjustment

A final spreadsheet containing one large total is difficult to evaluate without a record of the steps that produced it.

A reconciliation log makes those steps visible.

At minimum, a practical log can record:

1. The source file or database export.
2. The original record identifier.
3. The matching identifier used across systems.
4. The relevant measurement fields.
5. The inclusion or exclusion decision.
6. The reason for that decision.
7. The person or team responsible for reviewing exceptions.
8. The date and version of the reconciliation.

Where records are excluded as duplicates, preserve their original identifiers and the reference to the retained qualifying record. This provides a traceable explanation without destroying the underlying evidence.

For larger datasets, the same principle can be implemented through a controlled database query or repeatable data-processing script. The important point is that the method remains documented and reproducible.

Separate Data Preparation From Independent Review

The person preparing the consolidated total should not be the only person checking whether it is reasonable.

For a corporate submission, finance, operations, information technology or internal audit personnel may each contribute relevant knowledge.

A practical internal review can test whether:

• All eligible source systems have been identified.
• Overlapping systems have not been added together incorrectly.
• Matching rules are consistently applied.
• Excluded records have documented reasons.
• Reporting dates and time zones are consistent.
• The final total can be reproduced from the preserved data.
• Unresolved exceptions are disclosed rather than hidden.

Internal review strengthens the reliability of a submission, but it does not replace Asia Record’s own assessment or any record-specific verification arrangements.

Prepare a Clear Evidence Package for Asia Record

Once the data has been reconciled, the organisation should explain the proposed achievement in terms that can be assessed without requiring the reviewer to understand every detail of its internal software architecture.

A practical submission package may contain:

1. Achievement summary: A concise description of the proposed claim and the measured result.
2. Measurement definition: The exact unit, scope, period and qualifying conditions.
3. Source inventory: A description of the contributing systems and their responsibilities.
4. Reconciliation summary: Raw totals, confirmed duplicates, exclusions and the final qualifying total.
5. Matching methodology: The identifiers and rules used to determine whether records overlap.
6. Supporting extracts: Relevant original records and appropriately controlled supporting material.
7. Exception log: Unresolved cases, limitations and decisions requiring explanation.
8. Review documentation: Relevant internal confirmations or independent supporting information where appropriate.

This is an editorial preparation checklist, not a fixed list of mandatory documents for every Asia Record application. The exact evidence and assessment conditions depend on the proposed achievement.

Asia Record’s official application guidance asks applicants to identify the proposed title, applicant, achievement, measurement method, date, location and available supporting evidence. Additional clarification may be requested where information is incomplete.

Applicants can consult the official Asia Record application page for the nomination process.

Protect Confidential and Personal Information

Large datasets may contain customer details, employee information, commercially sensitive transactions or confidential partner records.

Preparing evidence does not mean that every underlying personal identifier should be circulated without restriction.

Organisations should establish appropriate access controls, assess their privacy and contractual obligations, and determine whether pseudonymised or limited extracts can support the relevant measurement.

Where a record must be independently checked, the organisation may need a controlled method for linking an extract back to its original source without exposing unnecessary information.

The evidence package should support the proposed claim while respecting applicable privacy, security and confidentiality requirements.

Common Mistakes When Combining Record Evidence

Adding Dashboard Totals Together

Dashboards may report the same underlying activity through different business functions. Adding them without checking their data lineage can inflate the total.

Assuming Every Matching Value Is a Duplicate

Two transactions with identical amounts may still be separate transactions. Matching decisions require sufficient identifying information.

Removing Duplicate Rows Without Preserving a Log

Deleting records without documenting the original entries and matching decisions makes the calculation harder to reproduce.

Mixing Different Measurement Definitions

Orders created, payments completed and shipments delivered represent different events. Combining them as though they are identical units produces an unreliable measure.

Ignoring Unresolved Records

Uncertain entries should be investigated or clearly disclosed. They should not automatically be counted merely because doing so increases the claimed achievement.

Changing the Method After Seeing the Result

A measurement rule chosen only because it produces a larger number can undermine the credibility of the claim. Definitions and material changes should be documented and justified.

When Is a Multi-System Achievement Ready for Submission?

A useful final test is whether a knowledgeable reviewer could independently follow the path from the proposed record title to the underlying evidence.

That path should be clear:

Defined achievement → identified sources → standardised records → documented matching → justified exclusions → reconciled measurement → preserved supporting evidence.

If a major step cannot be explained, further preparation may be necessary before relying on the final number.

Asia Record assesses proposed achievements according to their applicable conditions and evidence. A well-organised reconciliation can make a complex business claim easier to understand, but it does not guarantee recognition.

Organisations considering a measurable achievement can also review the official Asia Record Holder directory to understand how approved achievements are documented publicly.

Frequently Asked Questions

Can an Asia Record application use evidence from multiple systems?

An applicant may submit supporting information relevant to the proposed achievement. Where several systems contribute evidence, the applicant should explain their roles, measurement methods and any overlap. The exact evidence requirements should be confirmed for the proposed record.

Should duplicate records be deleted before submission?

Confirmed duplicates should not inflate a unique-unit measurement. However, preserving the original records and documenting which entries were excluded is generally more transparent than permanently deleting the evidence.

What if two systems report different totals?

Investigate whether the systems use different definitions, periods, processing stages or inclusion rules. A difference does not necessarily mean that either system is incorrect. The proposed record needs a clearly justified measurement method.

Can an Excel spreadsheet be used to reconcile record evidence?

A spreadsheet can be a useful working tool for smaller datasets. For larger or more complex submissions, a controlled database process may be more appropriate. In either case, preserve source records, document calculations and confirm record-specific requirements with Asia Record.

Does reconciling the data guarantee Asia Record certification?

No. Data reconciliation is one part of preparing reliable supporting evidence. Asia Record separately assesses the proposed claim, its measurement conditions and the supporting material before communicating a recognition decision.

Where can a company apply for Asia Record recognition?

Companies and other eligible applicants can begin through Asia Record’s official nomination page. The official website is AsiaRecord.com, which provides application information, verification guidance and the public Record Holder directory.

Turn a Reliable Measurement Into a Clear Record Proposal

A substantial business achievement deserves a measurement that can withstand careful examination. When several systems contribute to the same result, the strongest starting point is not the largest available total but a clearly defined figure supported by traceable records.

If your organisation has documented a measurable achievement across branches, systems or operating partners, review the official nomination process and prepare a clear explanation of how the result was calculated.

Submit Your Nomination to Asia Record