The right use case
- A is an older export.
- B includes A and adds new rows.
- You want to isolate what was added since the previous export.
- You have an order/invoice number or enough columns to recognize rows.
Added rows
When should you use “Rows added in file B”?
This mode is useful when file B is a newer or more complete version of file A. RGAnalyzer checks which rows from A are found in B, then isolates what remains to review.
In short
This is common with CRM, ERP, e-commerce or spreadsheet exports that include history and add the latest sales.
Simple method
What to check
The wrong use case
- Using this mode for two separate periods, such as Q1 and Q2.
- Assuming 100% of B is new without checking whether B includes A.
- Reading displayed rows as added sales when the mode does not fit.
RGAnalyzer
What RGAnalyzer checks
RGAnalyzer shows what the file can support and flags limits that may change the conclusion.
1
Share of A rows found in B.
2
Number of rows to review in B.
3
Recommended mode if files look more like two separate periods.
4
Clear warning when the mode cannot support a reliable conclusion.
FAQ
Frequently asked questions
Does B need to contain A?
Yes, for this mode to be truly relevant.
What happens if B does not contain A?
RGAnalyzer lowers confidence and recommends comparing two periods.
Is it useful without an order number?
Sometimes, but row recognition is less reliable and should be read carefully.