> ## Documentation Index
> Fetch the complete documentation index at: https://docs.m1amdocs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Transaction Lifecycle

General Transaction lifecycle:

1. Transactions can be generated from one of the following:
   * A Reseller (Service Provider) generated Transaction via Commerce Engine API for one-time purchase.
   * A Reseller (Service Provider) generated Transaction via Commerce Engine API of an initial recurring subscription.
   * Commerce Engine system generated recurring Transactions of an existing subscription.
   * A payment recorded in the system (when captured through cash or manual payment)

2. Use the Commerce Engine Portal to view your Transactions and their specific details.

3. Use the Commerce Engine Portal to keep up to 10,000 Transaction search results, by downloading to .csv file.

4. Use the Commerce Engine Portal to issue a refund on a captured Transaction.

5. Use the Transactions reports, available as part of the **Insights** menu, for an aggregated view of the Transactions over a period.

6. Keep a record of the Sales tax collected for different jurisdictions, use the **Sales Tax Detail Report** available as part of the **Insights** menu.

7. To reconcile settlements received from the payment processor with the billing performed in Commerce Engine, use the **Transaction Detail Report** available as part of the **Insights** menu.

   **Tip:** Commerce Engine Best Practice is to reconcile income on a monthly or quarterly basis. When comparing to a payment processor report, it is recommended that the reporting period for the payment processor data include one additional day to account for time zone differences and any delays in processor response. Data from both sources should match. Note that Payment processor transaction IDs are Commerce Engine TransactionIds in reverse.

8. To improve efficiency, you can review the refunds provided to customers and develop a best practice approach for your customer service representatives. Use the **Transaction Refund Detail Report** available as part of the **Insights** menu.

**Parent topic:**[Transactions](transactionAbout)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.