映射到您的账户图表

You can customize Stripe Revenue Recognition reporting to use your General Ledger (GL) chart of accounts instead of using the default Stripe accounts. You can configure a rule to map transactions by product, shipping region, or invoice metadata to your GL account. Stripe applies your custom mappings to the CSV reports you download and also when you audit your revenue numbers. A mapping rule consists of the following:

Configuring a mapping rule

Mapping rule configuration is a 4-step process—click the add mapping button on the accounts mapping page to begin.

1. Select Stripe account: Select the default Stripe account from the dropdown for which you want to create the rule.
2. Select GL account: You can select your GL account from the dropdown or add one if you can’t find it in the dropdown. When setting up the rules for the first time, you have to add these accounts by specifying the GL account name and number. You have to specify at least a name or a number to add the account.
3. Specify time period: The time period is the time frame in which the mapping rule is applicable. Select a start and end date from the dropdown to configure the time period. If you specify an time period that overlaps with closed accounting periods, you’ll see corrections in your report in the current open accounting period. You can reopen the past accounting periods corresponding to the time period to avoid corrections.
4. (Optional) Specify mapping condition*: You can specify a mapping condition on any of the following attributes:
   • Product: If you have product specific accounts in your GL, you can classify your transactions based on the products that you have configured in the Stripe Dashboard.
   • Shipping region: Similar to products, you can specify the shipping region to map transactions to the relevant GL account. Only ISO-compliant country and state codes are supported.
   • Invoice metadata: You can configure a custom rule using invoice metadata if your GL accounts don’t track transactions by product or shipping region. Create a rule by selecting a key and adding a value. The keys are from metadata you created in past invoices.**
   • Price: Use Price IDs configured in the Stripe Dashboard to map transactions to the relevant GL account.
   • Credit note: Specify the credit note line item description to map transactions to the relevant GL account.
   • Coupon: Use Coupon IDs configured in the Stripe Dashboard to map transactions to the relevant GL account.

Click Map chart of accounts to create the mapping rule and for Stripe to process the data. The rule’s status changes to active when the data processing is complete, and you can then download reports with the mapped GL accounts.

Mapping rule configuration example

The following example involves 3 different products:

• Product A: Annual subscription cost of 1,200 USD
• Product B: Annual subscription cost of 2,400 USD
• Product C: Annual subscription cost of 3,600 USD

If you sell 1 subscription each for A, B, and C in January, your journal entry at the end of the month appears as follows without account mapping:

However, the user has 3 separate revenue accounts in its GL, say revenue_A, revenue_B, and revenue_C for tracking revenue corresponding to these 3 products. The user has to do manual work to identify revenue in these accounts before posting to its GL.

If you have product-specific accounts in your General Ledger that you want to map to, you can create 3 mapping rules:

After you set up these rules, your journal entries will contain three line items reflecting the revenue distribution for each product. This can help you streamline the process of posting to your GL.

If you need to create multiple mapping rules at once, you can use our bulk account mapping feature to upload mappings via CSV file. This reduces manual effort and minimizes the risk of errors when configuring numerous GL accounts.