Income statement import
Income statement import
Model Documentation
Income Statement Import
The Income Statement Import tab lets you map your accounting system’s GL accounts to a P&L Category to be shown on the FS tabs. Some notes:
- It’s ok to include blank rows as well as total rows (as long as neither are tagged with categories).
- All positive amounts below are the normal balance that given account (e.g. revenue will be a positive number, as will payroll expense).
- Only months prior to and including the most recent actuals month (the input found on the “Update Checklist” tab) will be incorporated on the FS tabs.
- A good sanity check: compare the FS tab totals to this tab’s totals.
- If there’s a separate revenue line item you need to account for that isn’t captured anywhere else in the model, you can use the “Other Non-Recurring Revenue” row on the “Revenue” tab (and update it each month).
Account Mappings
If you choose “Default”, the Account Mapping table (on the “Advanced Inputs” tab) will handle allocations. You can also choose a different option to override the default.
For these P&L – Detailed Categories:
- “T&E”
- “Software Subscriptions”
- “Consulting & Outside Services”
- “Other”
The following options for P&L Line Item Category should not be selected:
- “Default”
- “Allocate based on department payroll”
- “Allocate to each P&L Line Item expense”
If you do choose one of these, they’ll simply go to “General and administrative”. If you need to allocate these to multiple P&L Line Item Categories, you can manually enter the same GL account on separate rows, tagging each row with a different P&L Line Item Category.
For the following P&L – Detailed Categories :
- “Interest (Expense) Income, net”
- “Other Income (expense)”
- “(Benefit from) income taxes”
You must select either the “Other Income (expense), net” or “(Benefit from) income taxes” P&L Line Item Category (otherwise the P&L won’t match the P&L – Detailed in aggregate).
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |