Specialized Services

AI Integration

AI integration is a workflow question before it is a technology question. We find the work that repeats every week, decide which steps a machine should do and which a person must, and build it inside the systems the business already uses.

Scope

A Defined Project, Not a Standing Retainer.

If you need the reporting itself, start with Accounting & CFO. If you have the reporting and need it to run with less handling, start here. The two are scoped and priced separately.

This Page · Automation Project

Map, build, hand off.

  • Workflow mapping and friction-point identification
  • Reporting-flow and data-handling design
  • Document, intake, and recurring administrative process redesign
  • Implementation inside your existing systems, with the exception rules and review steps written down
You receive
A working workflow, its documentation, the exception rules, and a handoff to the people who will run it. The project has an end date.

Ongoing Work · Accounting & CFO

The finance function that uses the output.

Monthly accounting, fractional CFO advisory, and the standing meeting at which the numbers are used are recurring engagements, scoped on their own page. An automation project often begins after that reporting exists, and sometimes the diagnostic there shows that a workflow project is what is actually needed.

Accounting & CFO services

Worked Example Illustrative

A Monthly Management Reporting Flow, Step by Step.

A representative workflow, not a specific client engagement. The output is the management reporting package shown on the Accounting & CFO page.

1 · Inputs

What comes in

  • General ledger export on close day
  • Bank feeds
  • Receivables and payables aging from the billing system
  • Payroll register
  • Budget workbook

2 · Automated steps

What the machine does

  • Pulls and reconciles the exports
  • Maps accounts to reporting lines
  • Computes variances and the KPI row
  • Drafts commentary where a variance crosses a threshold
  • Assembles the package

3 · Exceptions

What stops the line

  • Unmapped accounts
  • Variances over threshold with no explanation
  • Bank reconciliation differences
  • Duplicate or unmatched vendor invoices
  • Nothing proceeds until the queue is cleared

4 · Human review

What a person decides

  • The controller clears each exception
  • The practitioner reviews and edits the commentary
  • Sign-off is recorded
  • A change log keeps every edit

5 · Output

The management report

  • Delivered to the owner and the lender on the agreed day
  • Same format every month
  • Source files and the exception log archived with it

Selected Automation Work

Automate the Calculations First. Then Bring the Filings In-House.

Two pieces of work for a multinational group, at two different stages: one completed, one launched.

Completed · Calculation Automation

Led automation of foreign tax credit, BEAT, and book-to-tax calculations.

Three recurring tax calculations that had been assembled by hand from spreadsheets each period. The automated workflow, in the terms a finance executive would follow:

  1. Inputs. Trial balances by entity, intercompany payments, and fixed-asset and expense detail, pulled from the ERP and the provision system on a schedule.
  2. Calculation. Rules written once and applied the same way every period: the foreign tax credit limitation by category, the base erosion and anti-abuse tax (BEAT) computation, and the book-to-tax differences that feed the provision and the return.
  3. Exceptions. Unmapped accounts, unexplained period-over-period swings, and missing source data stop the line and go to a queue.
  4. Review. A reviewer clears the queue and signs off; the sign-off and every edit are recorded.
  5. Outputs. Workpapers to the provision, and figures to the return preparers, in the same format each period.

Launched · Broader Initiative

Launched an initiative integrating AI with the ERP system to bring certain non-U.S. return preparation and filing in-house.

A larger and separate undertaking from the calculation automation. Return preparation for certain non-U.S. jurisdictions had been outsourced; the initiative set out to map ERP data to the local return formats with AI assistance, with a reviewer controlling every filing. It is described here as launched, not completed, and its scope is limited to the jurisdictions selected for it.

The sequence carried into Firenze’s projects: automate the repeatable calculation first, keep a person on every exception and every filing, and scope the broader initiative only once the first workflow runs clean.

For a closely held company the equivalent is smaller: a sales-tax or 1099 workflow, a provision workbook, a monthly close. The pattern is the same.

What Happens Next

From Mapping to Handoff.

Step 1

Map the workflow

A short series of working sessions with the people who do the work. We trace what repeats, count the handoffs, and find where time and errors concentrate.

Step 2

Scope and build

A written scope: inputs, automated steps, exception rules, reviewers, and the definition of done. Then the build, inside your systems, tested against a real month.

Step 3

Hand off

Documentation, training for the people who run it, and a scheduled check-in after the first live cycle. The project closes when they no longer need us for it.

AI Integration

Scope an Automation Project.

Initial consultations are by referral or direct inquiry. We respond within one business day.