This report is a unique and powerful tool to assist you in monitoring the revenue from very large construction jobs. For any given job, you have costs and revenue. And, you have a profit margin. If your profit margin is 10%, then the revenue you receive should be 10% more than the costs you incur. The Job Revenue Analysis report allows you to ensure your profit margin is close to what you’ve planned for. If it isn’t, it’s an indication that costs haven’t been correctly billed. This report has the added benefit that it allows you to selectively filter out intercompany billing.
How does Abio map revenue to costs? The revenue map fields on each cost centre control how the costs and revenue are grouped in the Job Revenue Analysis report. You only need to set these fields on the standard centres. New centres will default to these revenue mappings, but you can override them. You can set these fields to the revenue centre used to bill that type of work, or you can enter a free-form description. For instance, you might want to group your centres into TRAIN, R&D, and WAGES (as an example).
One benefit of using revenue cost centres as revenue mapping groups is that the costs and revenue can map to the same revenue mapping group.
For example, you may post the scaffold labour costs to centre 16123, and scaffold revenue to centre 902. If you map the centre for posting costs, 16123, to the centre for posting revenue, 902, the Job Revenue Analysis report can measure your profit margin by showing the difference between postings for those two centres.
Parent and Shadow Jobs
It may be that you record your costs on a shadow job, and the revenue is recorded against a parent job. This report shows revenue and costs for both the shadow job and the parent job, and reports them under the parent job. Costs and revenue from Intercompany invoices can be filtered out by setting the predict type on the intercompany G/L account (see below).
Accounts payable invoices are recorded as costs in this report. They are mapped to revenue mapping groups according to which job/area/centre they are posted to. If the centre they are posted to doesn’t have a revenue centre mapped for their posting type (labour/materials/equipment/subcontract), then the revenue centre for the associated standard centre will be used for the report.
A/P invoices are divided into two groups:
These invoices are between vendors in one company and clients in another. Both vendor and client must be set up as intercompany vendors. These are vendors where the intercompany G/L field is set to a G/L account used to balance payments made to internal companies.
Control which intercompany invoices are reported by setting the predict type on the intercompany G/L to ‘primary’, if you want these invoices included, or ‘exclude’ if they shouldn’t be reported. Intercompany Invoices create A/P invoices in the source company and A/R invoices in the target company. Set the predict type to ‘E’ for the source company and ‘P’ for the target company so the two invoices don’t cancel each other out in the revenue mapping. In this example, we’ll exclude the intercompany invoices for the source company:
and include the invoices for the target company:
All other invoices are considered regular invoices. These types of invoices are included in the report regardless of the predict type coded on the associated G/L accounts.
Amounts from Accounts Receivable invoices are reported as revenue. Accounts receivable revenue is reported under it’s own centre. The exception to this is if the centre allows posting types in addition to ‘R’evenue. If it does, and one of the posting type matches the posting type of the A/R invoice, then the revenue will be reported under that revenue map.
Like the A/P invoices, intercompany invoices are reported separately from regular invoices. Invoices are identified as intercompany if the client has an intercompany G/L account populated.
Also like A/P invoices, you can select which side of the intercompany invoicing gets reported by coding the predict type on the intercompany G/L account.
Payroll postings are reported as costs on the Job Revenue Analysis. Note that this report reports the centres and costs from labour dispersions, not the original timesheets. If you’ve set up dispersion rules, your labour overheads will be reported as per the centre they were dispersed to.
Payroll is reported against the cost centre mapped for labour revenue, for the centre the payroll was originally posted to.
Journal entries posted to one of the Job Costing control accounts during the selected G/L period are reported as WIP (work in progress). Journal entries posted to ‘Costs’ accounts are reported as CST in the report.
Whereas journal entries posted to ‘Revenue’ accounts are reported as REV.
You control if a journal entry is included in the Job Revenue Analysis report by toggling the predict flag on the journal entry. If the predict flag is ‘Y’, the journal entry will be included in the report.
Job Revenue Analysis for a Single Company
This report can be run for a single company, or against a family of companies.
To run a Job Revenue Analysis report against a single company, navigate to [d] General Ledger, then [k] Job Revenue Analysis:
The criteria allow you to narrow down your job by G/L period, job, and/or region. You can also select to view only certain revenue mapping groups. You can also toggle whether or not you see G/L accounts with predict type set to ‘E’xclude, or not.
The company-based Job Revenue Analysis report shows the detailed breakdown of revenue and costs, grouped by revenue mapping group. The costs are subtotaled, then the revenue, and the difference between the two is displayed as the job total.
Note that you can click on any of the detail lines to see the source record. Invoice SLG-001 from SLEGGS for $56 is for this crescent wrench:
Job Revenue Analysis for a Family of Companies
The shared version of the Job Revenue Analysis report shows the same information, except summarized and across all the books for a single family of companies. If you are running a large industrial construction job distributed among several companies, this report is useful. It provides a consolidated view of the job’s revenue with intercompany invoicing filtered out.
To run the Shared Revenue Analysis report navigate to [h] Shared Reports, then [g] Shared Audit Reports, then [g] Shared Revenue Analysis:
The criteria lets you select a family, a G/L period to report up until, and a range of jobs. The report summarizes the amounts by G/L period. The criteria lets you select whether you’re reporting the most recent quarter, in which case there is a column for each of the months in the quarter. You can also select half year. In that case, each column displays two G/L periods. If you select a full year, then each column displays the sum of four G/L periods.
The Shared Revenue Analysis shows the same data as in the version for a single company, but summarized. It also shows subtotals for each job in each company, and then a total for the job across all companies. In our example we’re only running the jobs in single companies, so the company total and the job total are the same. The cost total is displayed, then the revenue. The company total shows the revenue less the costs for that company. The job total shows the revenue less the costs for that job across all companies in the family.