For an imported transaction to match with an end-user's manually created draft expense the following system rules must be met:
Purchase method must match.
The manually created draft expense amount (ExpenseIn account base currency value) entered needs to be an exact match with the amount imported. If the draft expense is for a foreign amount an exact match on the imported local/original amount and the currency code is required.
The merchant name needs to be close to an exact match.
The purchase expense date needs to match or can be within two days ahead of the original purchase date as long as the above criteria are met first. This is to allow merchants and banks time to process the purchase data.
For an imported transaction to match with an unattached receipt the following needs to match:
Purchase method must match.
The purchase receipt amount needs to be an exact match with import amount. If the receipt is for a foreign amount an exact match on the imported local/original amount and the currency code is required.
The merchant name needs to be close to an exact match.
The purchase expense date needs to match or can be within two days ahead of the original purchase date as long as the above criteria are met first. This is to allow merchants and banks time to process the purchase information.
If the above rules are not met when a card statement import is completed, your end-users will need to manually attach the correct receipt to the imported draft expense created or merge the imported draft expense with a manually created one.