Previous	Next		Contents	Index	Navigation	Glossary	Library

During Payables Open Interface Import, Payables converts transaction distributions into invoices with distributions. When you load transactions from the card issuer, each transaction has one distribution. You can use this window to split a transaction distribution into multiple distributions which you can then process separately. For example, an employee receives a bill for a hotel room. Instead of charging the $100 corporate rate, the hotel charged $130. You can create two distributions for the transaction, one for $100, and one for $30. You can assign a status of Disputed for the $30 transaction and process the $100 distribution as usual.

Attention: To prevent payment of a transaction distribution with a status of Disputed, you also need to check the Disputed checkbox in the Don't Pay If Status region of the Credit Card Programs window. See: Credit Card Programs.

Card holders can create multiple distributions per transaction in the Open Credit Card Transactions page of Web Employees. You can also use the Distributions region of the Credit Card Transactions window in Payables to split distributions. The total amount of the transaction distributions must equal the transaction amount.

Transaction Date. Date that the transaction posted to the credit card account.

Reference Number. The reference number that the card issuer assigned to the transaction.

Currency. Currency of the credit card statement.

Amount. Amount of the transaction in the credit card statement currency.

Card Program. Card program assigned to the credit card used for the transaction.

Card Code. Credit card code (supplier or supplier type) of the transaction.

Employee Name. Card holder's name.

Merchant Name. Merchant that processed the transaction.

Transaction Distributions

• Approved. All approvals are complete and the transaction is ready for import.

• Disputed. A card holder or manager assigns this status to a distribution to indicate that there is a dispute over the transaction.

• Hold. A card holder assigns this status to a distribution to indicate that there is a problem with the transaction.

• Personal. A card holder uses this status to indicate that a transaction was personal.

• Rejected. Workflow assigns this status to a transaction if the manager denies approval for the transaction.

• Validated. The Credit Card Transaction Validation and Exception Report assigns this status to a transaction if it was successfully validated.

• Verified. Either in the Credit Card Transaction Verification page or by using workflow, the card holder has verified the transaction.

Account. Account to which the transaction distribution will be charged. The Credit Card Transaction Validation and Exception Report builds accounts depending on how you set up your card profile. Card holders can change the default account by using the Credit Card Transaction Verification page. In addition, you can override the account in this window.

Description. Description of the transaction distribution. This will be the invoice distribution description (unless you summarize by GL Account when you submit the Credit Card Invoice Interface Summary).

Account Description. Payables displays the description of the account.