CAO admissions ad spend per programme reconciliation works one way: each invoice line item maps to a campaign ID tied to a CAO course code, or to the HEI's internal programme code where no CAO code exists. Multi-programme campaigns split by impressions share or by landing-page conversions. Spend pulses follow the CAO cycle — an October to late-January early-bird wave carrying applicants to the 1 February deadline, then a May to August Change of Mind, final-deadline and Round 1 wave from the 5 May opening through the 1 July final into the August offer rounds. The per-programme totals feed both the management-accounts marketing line and the per-programme cost data that sits beside the HEA Student Records System returns submitted in November (provisional) and March (final), with a 1 March census date.
The reconciliation runs across three supplier categories. Meta Platforms Ireland Ltd issues consolidated monthly invoices that itemise spend by campaign. Google Ireland Ltd issues ad invoices that go a level deeper, exposing campaigns and their ad groups. Then there are the digital agencies on the HEI's panel — Wolfgang Digital, Beyond, PHD Ireland, Mediaworks, Verve and similar — issuing managed-service retainers and pass-through media charges that often need a working-paper split back to platform before the per-programme allocation can begin. All three are domestic Irish supplies. The VAT sits on the face of the invoice in EUR; there is no reverse-charge step.
A single CAO cycle's spend straddles two HEI financial years, which is what makes this a cross-year working paper rather than a within-month posting. The same spreadsheet feeds three downstream consumers: the per-programme management accounts the management accountant posts at month-end and year-end, the per-programme cost data that sits in the HEA SRS submission window, and the budget committee's review of the next cycle's allocation, where per-programme cost-per-acceptance and cost-per-enrolment figures argue for or against next year's faculty-by-faculty splits.
The CAO Cycle as the Spend-Pulse Calendar
The cycle has four anchor moments and the marketing-finance calendar is built around them: the 1 February normal-application deadline, the 5 May Change of Mind opening, the 1 July final application deadline, and the August Round 1 and Round 2 offer rounds. The structural shape is stable; the cycle-year-specific exact dates shift slightly each year and should be confirmed against the CAO's published key-dates page rather than baked into evergreen working-paper templates.
Two pulses of paid-media spend run against that cycle. The first runs from October to late January — early-bird and awareness campaigns carrying Leaving Cert applicants toward the 1 February deadline. This is when most of the cycle's awareness budget goes out the door, and most of it lands on Meta and Google brand and prospecting campaigns. The second pulse runs from early May to mid-July, with the 5 May Change of Mind opening as its trigger, reinforcement spend through the 1 July final deadline, and Round 1 offer-round campaigns running into August. The two pulses have different creative briefs and different audience definitions, but they share the campaign-tag taxonomy that lets the working paper reconcile them later.
A single CAO cycle's spend lands across two HEI financial years. An institution on a 1 January year-end sees pulse one straddle two financial years (the October–December portion in the prior year, January carrying into the new one); an institution on a 1 September academic-year alignment sees pulse two split similarly. Either way, the working paper has to carry across the year-end cut-off, and the column structure of the per-programme spreadsheet has to make the financial-year boundary obvious on the face of the sheet so the management accountant can post the right slice in the right period.
The vocabulary the reader will see in campaign tags and creative briefs mirrors the cycle: Leaving Cert applicant, Change of Mind, Round 1 reinforcement, August offer round. Most HEI ad-account taxonomies — whether the campaigns were built in-house or by an agency — adopt this vocabulary because it matches how the admissions marketing manager briefs the work. When the campaign-name string carries the cycle phase alongside the programme code, the reconciliation gets straightforward at Tier 1.
Two smaller spend nodes fall outside the two main pulses but belong on the same per-programme spreadsheet. Spring postgraduate and mature-student campaigns run on the Postgraduate Applications Centre and direct-application calendars, which overlap the CAO cycle without sharing its cadence. Springboard+ ringfenced-funded programme campaigns run on the HEA and SOLAS Springboard+ calendar, with its own intake windows. Both belong in the same spreadsheet — the per-programme totals at year-end need them — but they sit in their own cycle columns rather than folded into the CAO pulse columns, so the methodology applied (and the audit trail) can stay specific to each calendar.
The Per-Programme Spreadsheet Shape
Each programme is a row, keyed twice. The CAO course code where one exists — every undergraduate honours and ordinary degree programme will have one; level-6 and level-7 programmes will have one; level-9 and level-10 postgraduate programmes generally will not. The HEI's internal programme code from the management-accounts chart of accounts is the second key, and is the one that ties back to the ledger when the management accountant posts the marketing line. Programmes without a CAO code — postgraduate, Springboard+, CPD short courses — carry only the internal code and are flagged on the row so the absence of a CAO code is intentional rather than a missing-data error.
The columns map directly onto the spend-pulse calendar. An Oct–Jan early-bird column for pulse one, a Feb–Apr inter-pulse column to capture postgraduate and mature-student campaigns that run on the PAC and direct-application calendars, a May–Jul Change of Mind and final-deadline column for pulse two, and an Aug offer-round column for the Round 1 and Round 2 reinforcement spend. Each pulse column splits into sub-columns by supplier and platform: Meta, Google Search, Google Display / YouTube / Discovery, and one column per named agency, with each agency line further split between agency-fee (managed-service or retainer) and pass-through media. The sub-column structure is what lets the working paper reconcile back to invoice gross at the supplier level, not just at the programme level.
Beside each pulse-column figure sits a small block of working-paper fields that make the allocation auditable. The gross spend figure itself, the allocation method tag for that figure (campaign-tag, impressions-share, landing-page, or manual), the source invoice reference (invoice number plus line number), and a per-row total that ties to the sum of underlying invoice line items. The reconciliation is the discipline: the sum of the spend figures across all programme rows for a given supplier-and-pulse cell must equal the supplier's invoice gross for that pulse, and any variance has to be resolved before the spreadsheet leaves the marketing finance officer's desk.
The dimensional fields a management accountant needs to post the marketing line cleanly belong on the row alongside the codes. Faculty or school grouping, programme level (undergraduate, taught postgraduate, research postgraduate), funding source (HEA core, Springboard+, full-fee, international), and the financial year each pulse column belongs to. The financial-year field is what makes the cross-year cut-off obvious on the face of the sheet — the management accountant should not have to read the column header to know which postings belong to which year.
A small worked example makes the shape concrete. Take a BSc in Computer Science with a CAO code (CK101 in the example) and an MSc in Data Analytics without one (internal code MU-MSCDA). Three suppliers ran in pulse two: a Meta campaign tagged for CK101 specifically, a Google campaign tagged for the Faculty of Engineering with ad groups split per programme, and an agency that ran a Change of Mind campaign promoting both the BSc and the MSc together with a single landing page covering both. The Meta line allocates 100% to CK101 at Tier 1. The Google campaign's ad-group split allocates each ad group cleanly at Tier 1 once unfolded. The agency's pass-through media line allocates between CK101 and MU-MSCDA at Tier 2 by impressions share — the campaign's impressions report gives the percentage split — and the agency's retainer line for the period allocates pro-rata to that pass-through split. Two rows on the spreadsheet, four cells filled, four method tags stamped, four source-invoice references recorded, and a clean tie back to invoice gross.
Pulling Line Items Off Meta, Google, and Agency Invoices
Each supplier's invoice exposes a different shape of detail, and the working paper needs different fields from each.
Meta Platforms Ireland Ltd consolidated monthly invoices. The header carries the billing month, the Meta ad account ID (or multiple ad account IDs where the HEI runs separate accounts for undergraduate, postgraduate and Springboard+ campaigns), and the gross / VAT / total totals for the month. Below the header, the line items break down by campaign — the campaign name is the field that does the work for the per-programme allocation, because that name is where the campaign-tag taxonomy lives. If tagging discipline held during the cycle, the campaign name carries the CAO course code or the internal programme code in its string. Pull each line: campaign name, gross EUR, VAT EUR, period the campaign ran. Carry the ad account ID through onto the working-paper row as well — when the HEI runs multiple ad accounts, the account ID is the first sort key for the reconciliation and the audit trail. Once the per-cycle stack of consolidated invoices is in front of you, extract Meta Ads invoice line items to Excel using whichever method gets you a clean per-campaign row structure with those five fields.
Google Ireland Ltd ad invoices. Google's invoice opens with a billing summary, then gives an itemised list of campaigns, with each campaign's spend split out by ad group underneath. The ad-group level is where Google's allocation is genuinely useful: a single faculty-wide campaign — say a "Faculty of Engineering — Change of Mind" campaign — can carry per-programme ad groups, and when ad-group naming was disciplined the per-programme allocation falls out at Tier 1 without any impressions-share work. The fields to pull are campaign name, ad-group name, gross EUR, VAT EUR, customer ID, and the period the ad group accrued spend in. The granularity matters: the ad-group level is what makes Google's invoices the easiest of the three to allocate per programme when ad-group naming was disciplined, and it is also what makes the line-item count balloon. A single CAO cycle's Google ad invoices can run to several hundred ad-group rows once unfolded, which is why the working paper needs a structured extraction step rather than a manual transcription. The same shape — campaign-and-ad-group rows with the gross, VAT, customer ID and period on each — is what you need to convert Google Ads invoices to a structured spreadsheet for the per-programme allocation that follows.
Irish digital agency invoices. The shape varies by agency and by contract, but the typical pattern is a managed-service or retainer fee for the period, then pass-through media charges that may or may not be itemised by platform. Where the agency itemises pass-through media — a Meta line, a Google line, sometimes a programmatic display line, sometimes a TikTok line — the invoice can be reconciled against the Meta and Google invoices the agency operated, line by line, and the per-programme allocation runs on the same campaign-tag basis as the platform invoices. Where the agency aggregates pass-through into a single "media spend" line, the working paper has to request a media-spend breakdown from the agency before allocation can begin. This is a routine ask on Irish HEI agency contracts and most agencies on the panel — Wolfgang Digital, Beyond, PHD Ireland, Mediaworks, Verve are the relationships you are most likely to be reconciling against — will produce a per-platform breakdown on request. Set the request up as a recurring monthly deliverable rather than a per-cycle ask; it shortens the autumn reconciliation considerably.
The volume problem is what makes this the part of the cycle that consumes a marketing finance officer's autumn. Across a single CAO cycle, an HEI accumulates 12 to 24 Meta consolidated invoices (depending on how many ad accounts it runs), a comparable run of Google ad invoices, and monthly invoices from each agency on the panel. Once campaign and ad-group rows are unfolded, that is several hundred line items in total, and each line carries the five or six fields the per-programme spreadsheet needs.
Converting that stack of supplier PDFs into a structured per-line-item spreadsheet is exactly what an AI invoice data extraction for ad and agency invoices workflow handles end-to-end. Upload the cycle's Meta, Google and agency PDFs as a single batch — the platform takes batches of up to 6,000 files and single PDFs of up to 5,000 pages, well above any HEI's cycle volume — prompt for the per-line-item fields the working paper needs (campaign name, ad-group name where present, period, gross EUR, VAT EUR, ad account or customer ID, agency name where applicable), and download a structured Excel or CSV output keyed by campaign and period that drops straight into the working paper. Save the prompt to the prompt library after the first cycle and reuse it next year — the field shape repeats every cycle, and the reusable prompt is what makes the second year's extraction a same-day job rather than another autumn project. Each row in the output also carries a reference back to the source PDF and page, which is exactly the source-invoice-reference field the per-programme spreadsheet needs for its audit trail.
Allocation Methodology in Priority Order
Once the line items are in the working paper, each one has to be allocated to a programme. The methodology is a four-tier hierarchy with a clear audit rationale at each tier, and the allocation method tag stamped into the working-paper cell records which tier produced the figure.
Tier 1 — Campaign-tag-to-programme mapping. The clean path. When the campaign name encodes the CAO course code or the internal programme code — a campaign called something like UCC-CK101-CompSci-CoM-2026 carrying the CAO code, or MU-MSCDA-Spring-2026 carrying the internal code — every line item under that campaign allocates 100% to that programme and the cell stamps campaign-tag. The precondition is a tagging convention set at brief stage and held across the cycle. Most HEIs have this convention written into the marketing-operations policy; tag discipline at execution varies. In practice the cycle's reconciliation almost always sees a mix of clean-tagged and ambiguous campaigns, and the value of disciplined Tier 1 tagging is that it shrinks the share of the cycle's spend that has to go through Tiers 2 to 4.
Tier 2 — Impressions-share split for multi-programme campaigns. When a single campaign promoted a faculty or course family rather than a single programme — the agency's Change of Mind campaign in the worked example covered both the BSc and the MSc on a single landing page — the spend allocates by the campaign's impressions share to each programme's targeting or landing-page conversion path. Pull the impressions data from the platform: Meta Ads Manager exposes impressions per ad set and per ad, Google Ads exposes impressions per campaign and per ad group, and most agency-operated campaigns will surface the same data through the agency's reporting layer. Apportion the campaign's gross spend across programmes by impression share and stamp impressions-share into the working-paper cell. Impressions share is a defensible proxy for marketing intent at the campaign level; it is not the same as conversion attribution, but it is the strongest upstream-targeting signal available on the platform and an internal auditor or budget-committee chair will recognise it as such.
Tier 3 — Landing-page-family split. When impressions data is not accessible — for instance because the agency ran the campaign and only ad-account-level data is available, or because the campaign was retired and platform-side reporting is no longer queryable — fall back to landing-page conversions: the proportion of the campaign's clicks or conversions that landed on each programme's URL family on the HEI website. GA4, Plausible, Matomo, whichever the HEI runs, is the source. The audit rationale here is downstream-behavioural rather than upstream-targeting, which is a meaningful step weaker than Tier 2 — applicants who clicked through to a programme page are not the same population as the audience the campaign targeted — but it is the strongest available proxy when upstream targeting data is opaque, and stamping landing-page into the cell tells the auditor exactly which proxy was used.
Tier 4 — Manual judgement allocation with audit-trail entry. The last resort, and the tier where audit defensibility lives or dies. When campaign-name evidence, impressions data and landing-page data are all unavailable or ambiguous, the marketing finance officer makes a judgement call — typically by consulting the admissions marketing manager who briefed the campaign — and records it as a discrete entry in the working paper's audit trail. The audit-trail entry has to contain six fields, every time: the line item being allocated (invoice number, line number, gross EUR, period); the programmes the spend is being split between (each with its CAO code and / or internal code); the percentage split per programme; the basis for the judgement (briefer's note, prior-cycle pattern, equal default, or whatever the substantive reason is); the date of the entry; and the name of the person making the call. An auditor or budget-committee chair will accept a manual allocation with this trail; they will reject one without it, and the difference at sample-time is whether the cycle's marketing posting holds up or has to be reopened.
Agency retainer fees. The four-tier hierarchy applies to media spend. Agency retainer or managed-service fees are not media spend — they are the price of operating the underlying media — so they do not split by impressions or landing-page. The conventional treatment, which most internal audit functions accept and which is also the methodology to reconcile advertising agency retainer and pass-through invoices more generally, is to allocate retainers across programmes pro-rata to the pass-through media spend the agency operated for each programme during the same period. Stamp pro-rata-retainer into the cell; the rationale is that the retainer is contingent on and proportional to the underlying media work, so its per-programme split should follow the media split. Where the retainer covers a longer period than a single pulse — quarterly retainers are common — split the retainer to the pulse first, then apply the pro-rata-to-media allocation within each pulse.
Schedule 1 and Section 61 VAT on the Same Spreadsheet
The Irish VAT call on advertising input runs on the same per-programme spreadsheet, not as a parallel workstream. Working it as a separate exercise duplicates effort and produces an apportionment denominator that does not tie back to the marketing posting; running it on the same spreadsheet is the efficient path.
Irish higher-education institutions are Recognised Bodies under Schedule 1 of the Value-Added Tax Consolidation Act 2010. The supply of education by a Recognised Body is VAT-exempt, and inputs used wholly for the supply of education carry no input deduction. That is the starting point and it covers most of an HEI's CAO admissions advertising — campaigns promoting an undergraduate honours degree are inputs directly attributable to the supply of education, and the input VAT on those line items is non-deductible.
The complication is that almost every Irish HEI also has taxable activities. Research services delivered to industry, conference services, commercial training and CPD short courses sold on a fee basis, retail (campus shop, parking, vending), facilities hire, and sometimes consultancy income — these are taxable supplies. Inputs used partly for the exempt supply of education and partly for taxable activities are dual-use, and Section 61 VATCA 2010 requires the HEI to apportion the input VAT on those dual-use inputs via a methodology it can defend.
The doctrine lands on advertising input three ways. A campaign promoting an undergraduate or taught-postgraduate programme delivered as exempt education is directly attributable to the exempt supply — the input VAT on that line item is not deductible. A campaign promoting a CPD short course or a commercial training programme that the HEI delivers as a taxable supply is directly attributable to that taxable supply — the input VAT on that line item is deductible. A campaign promoting a programme family that contains both exempt and taxable supplies — for instance a Faculty of Business campaign covering both an exempt undergraduate degree and a taxable executive-education short course — is dual-use and apportions under Section 61.
The operational consequence is that per-programme allocation is the upstream input to the VAT decision, not a separate spreadsheet. Each line item, once allocated to a programme, takes on that programme's VAT status — exempt-supply, taxable-supply, or dual-use — and the input-VAT recovery position falls out of that classification. Add a VAT-status column to the per-programme spreadsheet, populate it from the programme master file, and the VAT3 input-VAT line for the period derives from the same data set as the marketing posting. The reconciliation that ties marketing-posting gross to invoice gross also ties recoverable VAT to invoice VAT, with the dual-use slice carved out for apportionment.
The supplies themselves are domestic. Invoices from Meta Platforms Ireland Ltd, Google Ireland Ltd and Irish-resident agencies are domestic Irish supplies, so there is no reverse-charge mechanism on these invoices — Irish VAT is on the face of the invoice in EUR, and the input-VAT decision is made on the invoice as issued. This differs from the reverse-charge treatment HEI finance teams may be more familiar with from non-Irish ad platforms (e.g., LinkedIn Ireland Unlimited Company has the same domestic treatment, but a US-issued invoice from a non-Irish platform would shift to reverse charge). The practical implication for the working paper is that the VAT amount on each Meta, Google and Irish-agency line item has to be carried into the spreadsheet alongside the gross — not assumed to be zero on a reverse-charge basis. The face-of-the-invoice VAT also has to comply with the Irish VAT invoice requirements and mandatory fields that govern any Irish VAT invoice; in practice the platform invoices comply by default, but the working paper should still confirm the supplier's Irish VAT number and the invoice's mandatory fields are present before relying on it for input VAT.
The methodology question is largely answered by the HEI's existing apportionment policy. Revenue Commissioners accept a range of dual-use apportionment methodologies — turnover-based, floor-area-based, headcount-based, input-based — provided the methodology is consistent, documented, and reviewed periodically. Most Irish HEIs operate a turnover-based apportionment, agreed historically with Revenue, and the per-programme spreadsheet feeds that policy's denominator inputs (the programme-level taxable and exempt turnover figures) rather than choosing a new methodology. The advertising-input apportionment is governed by whatever the HEI's general apportionment policy already says; the per-programme spreadsheet's job is to land each line item against the right programme and the right VAT status so the policy can compute the deductible slice cleanly.
Handover to Management Accounts and the HEA SRS Return
The per-programme spreadsheet has three downstream consumers and the marketing finance officer's job is to deliver to each of them in the shape and timing they need.
Management accounts. The per-programme totals post to the management-accounts marketing cost line, dimensioned by programme code, faculty or school, and funding source. Most HEIs run management accounts monthly and most operate on a 31 August or 31 December year-end depending on whether the institution is calendar-year or academic-year aligned. The reconciliation produces an opening month-end posting once the cycle's main pulses have cleared and an updated posting once the late-arriving agency invoices clear (agency invoices for August offer-round campaigns often arrive into October or November, so the year-end accrual has to be carried as a journal until the actuals land). The marketing finance officer's working paper is the audit-trail backing for the management-accounts entry — when the management accountant or external auditor questions the marketing line, the working paper is what answers them, line by line. The same per-programme data shape works whether the institution treats this as part of its broader AI invoice processing for schools and universities workflow or runs the marketing reconciliation as a standalone job.
The HEA Student Records System return. Higher education institutions submit Student Records System (SRS) returns to the HEA twice a year — provisional in November and final in March — with a census date of 1 March. That calendar is set out on the HEA SRS return calendar page, and it is the timing the per-programme cost data has to feed. The SRS return itself carries student-level data by programme, but the per-programme cost data the HEI assembles in the same window — including the marketing line — feeds the wider HEI accountability framework that surrounds the SRS submission. System Performance Framework metrics, Funding Allocation Model inputs, governance reporting to the institution's governing authority, and HEA-published per-programme cost benchmarking all draw on the same per-programme cost picture. The marketing line is one component of that picture, and a defensible allocation methodology is what makes it auditable in the same way the academic and administrative cost lines are.
The budget-committee review. This is the third downstream use of the same spreadsheet, and the one the marketing finance officer's reconciliation methodology pays back for most directly. Per-programme spend, per-programme CAO acceptances and the yield-to-enrolment rate combine into per-programme cost-per-acceptance and per-programme cost-per-enrolment figures — the per-programme advertising ROI numbers that drive next cycle's budget allocation. When the committee asks why the Faculty of Engineering's CAO Round 1 cost-per-enrolment ran materially above the Faculty of Arts figure, the answer has to come from the spreadsheet's allocation tags, the audit-trail entries, and the briefer's notes. A reconciliation built on Tier 1 and Tier 2 evidence with audit trails on the Tier 4 allocations gives the committee a defensible answer. A reconciliation built on a stack of unrecorded judgement calls does not.
The deliveries land at different points in the year and the marketing finance officer's calendar has to plan for each of them. The provisional management-accounts marketing posting feeds the year-end close — for a 31 December year-end that means a January or February delivery once the cycle's late agency invoices clear; for a 31 August year-end the delivery is October or November of the same calendar year. The final per-programme cost data, with all late agency invoices reconciled, supports the March HEA SRS final return. The budget-committee review typically lands in October or November, once the cycle's final enrolment is confirmed and the cost side has settled. The same spreadsheet serves all three — the difference is which slices and which dimensions the consumer needs at each point.
When Tagging Discipline Breaks: Audit-Trail-Defensible Manual Allocations
Tag discipline is what makes the post-cycle reconciliation tractable, and it is also what fails most often. The autumn job feels disproportionate to the underlying spend because the reconciliation surfaces every tagging gap from the cycle at once, and the marketing finance officer absorbs the cost of each.
The common failure modes are predictable. A campaign launched without the programme code in the campaign name — the brief named the programme but the tag did not. Agency-built campaigns using the agency's internal taxonomy rather than the HEI's, so the campaign name encodes the agency's project code rather than the CAO course code. Mid-cycle reorganisations of campaigns under new names that break the tag-to-programme mapping the working paper had been holding. Ad-group-level tagging that contradicts the campaign-level tag, with the ad group naming a programme the parent campaign did not. A working paper built on Tier 1 evidence runs into all of these, and the work shifts from clean per-programme allocation to triage.
The procedure for the cycle being reconciled has three steps. Cluster the ambiguous campaigns by their landing-page family, which puts each campaign on the right programme or programme set even when the campaign name does not. Corroborate the clusters with the admissions marketing manager who briefed the campaigns — the briefer often remembers exactly which programme a campaign was for and can confirm or correct the landing-page-derived clustering in a single conversation. Produce manual judgement allocations for any campaigns that remain ambiguous after both, and write the audit-trail entry as a row-level deliverable in the working paper itself rather than as a side note. The audit trail is the deliverable the committee and the auditor will look for; treating it as a working note hides the work that justifies the figure.
Each audit-trail entry needs the same six fields, every time. The line item being allocated — invoice number, line, gross, period. The programmes the allocation splits between, each with its CAO course code and / or internal programme code. The percentage split per programme. The basis for the judgement: briefer's confirmation, landing-page family pattern, prior-cycle allocation pattern, equal default, or whatever the substantive reason was. The date of the entry. The name of the person making the call. A spreadsheet that carries this row for every manual allocation is defensible at sample-time; one that does not is an unresolved finding waiting to happen.
The budget committee will not interrogate every allocation in the cycle, but it will sample. The samples that get challenged are the largest manual allocations and the ones that contradict what the admissions marketing manager remembers about a specific campaign. The defensible answer is the audit-trail entry — the methodology tier applied, the basis for the judgement, the briefer's involvement, and the date the call was made. Without that record the answer becomes an after-the-fact reconstruction, and committees recognise the shape of those answers and discount them. The audit-trail entry is a one-line deliverable; the absence of one is a re-opened reconciliation.
The forward fix is a small set of changes that compound over the next cycle. A published campaign-naming convention with the CAO course code and / or internal programme code as a required field, applied at brief stage and enforced before campaigns go live. A brief-stage approval gate where marketing finance signs off on the proposed tag taxonomy for the cycle's campaigns alongside the marketing approval. An agency contract clause requiring the HEI's tag taxonomy on every agency-built campaign — not the agency's own project codes — and a corresponding requirement that the agency's monthly invoice references those same campaign names. A mid-cycle tag-discipline check in June, while the cycle is still running, surfaces the gaps when there is still time to rename campaigns and apply tags retrospectively at the platform level rather than absorbing the cost as manual allocations at the post-cycle reconciliation. None of these are heroic interventions; together they shift the reconciliation from a triage exercise back into a Tier 1 job, and the autumn marketing finance project from several weeks of allocation work into a few days of tying out totals.
Extract invoice data to Excel with natural language prompts
Upload your invoices, describe what you need in plain language, and download clean, structured spreadsheets. No templates, no complex configuration.
Related Articles
Explore adjacent guides and reference articles on this topic.
NPA Monthly Invoice Extraction to Excel by Student
Extract NPA monthly invoices to Excel with student-level service minutes — IEP-authorized vs delivered, rate tier, and service type — across multiple states.
School District Related-Services Invoice Spreadsheet Guide
Prepare a school district related-services invoice spreadsheet with student, service, provider, and upload fields from invoices and service logs.
DHH Interpreter Invoice Extraction to Excel
Extract DHH interpreter invoices and service logs into Excel with assignment rows for dates, PO, student, hours, mileage, rates, and reconciliation.