Jump to main content
Secure Processing Taiwan Operations
FirelyX Logo

Questions We Hear Most

Setting up financial reporting automation brings up practical questions. We've organized answers by where you are in the process — from initial curiosity through implementation and beyond.

Answers Organized by Your Journey

Different stages bring different questions. Here's what clients typically ask before they start, during setup, after going live, and when they're expanding what they've built.

1

Before You Start

  • How long does initial setup actually take?
  • What access do you need to our existing systems?
  • Can we test with one department first?
  • What happens to our current reporting process during transition?
  • Do we need to change our chart of accounts?
2

During Implementation

  • How do we handle historical data migration?
  • What if our data structure doesn't match standard formats?
  • Can we adjust reporting templates mid-project?
  • How often will we meet during the setup phase?
  • What training do our staff need to receive?
3

After Going Live

  • What support is available when we encounter issues?
  • How do we add new report types later?
  • Can we modify automated schedules ourselves?
  • What happens during system updates or maintenance?
  • How do we handle staff turnover and new user training?
4

Growing Your System

  • How do we integrate additional data sources?
  • Can we connect multiple legal entities later?
  • What's involved in adding consolidation reporting?
  • How do we scale as transaction volume increases?
  • Can we build custom dashboards for specific users?
Financial reporting workflow implementation in progress

Real Implementation Example

A manufacturing client in Kaohsiung needed to automate monthly reporting across three entities. Their main concern? They had 15 years of Excel-based reports with specific formatting their board expected.

We maintained their familiar report layouts while automating data population. Setup took six weeks instead of the eight we estimated — they had cleaner source data than expected. They still get reports that look exactly how their board wants them, just without the manual work.

Detailed Answers to Specific Questions

These are the questions that come up repeatedly in discovery calls. Not the basic stuff — the practical concerns that affect your decision and implementation experience.

Technical Setup

What accounting systems do you work with?
We connect with most ERP and accounting platforms common in Taiwan — SAP, Oracle, local systems like Cosmos and Ares. If your system can export data or has an API, we can work with it.
Do you host our data or does it stay with us?
Your data stays in your systems. We build connections that pull what's needed for reports, process it, then deliver results back to you. We don't store your transactional data.
Can we handle this ourselves after setup?
That depends what you mean by "this." Running reports and making template adjustments? Absolutely. Rebuilding data connections or major workflow changes? Most clients prefer we handle those, though we can train technical staff if you want.

Timeline and Process

What's a realistic timeline for basic automation?
For standard monthly reporting from one accounting system, figure 4-6 weeks from kickoff to first automated report. Complex consolidations or multiple data sources can take 8-12 weeks. Rush projects are possible but rarely go well.
How much of our time does implementation require?
Expect weekly meetings during the first month — usually an hour each. Your finance team needs to review test reports and provide feedback. Total time commitment runs 15-20 hours for key staff over the project.
What if we need changes after the initial setup?
Minor template adjustments are usually included. New report types or data source additions would be separate work. We typically see revision requests in month two or three as you discover what else you want automated.

Data and Accuracy

How do we verify automated reports are correct?
We run parallel reports during testing — your manual process alongside our automation. You verify they match before we go live. Most clients continue spot-checking for a few months until they're comfortable.
What happens if source data has errors?
Automation reports what's in your system. If source data is wrong, reports will reflect that. We can build validation checks that flag unusual values or missing transactions, but the automation won't fix data quality issues.
Can we audit the calculation logic?
Yes. We document all formulas, transformations, and business rules. Your auditors can review this documentation. Some clients want their IT team to inspect the actual code, which we can arrange.

Costs and Resources

What affects the cost of a project?
Complexity of data sources, number of report types, custom calculations, and integration requirements. A single-entity P&L automation costs much less than multi-entity consolidation with eliminations.
Are there ongoing costs after implementation?
Support and maintenance typically run monthly. This covers system monitoring, minor adjustments, and help when issues come up. Most clients also budget for periodic enhancements as needs evolve.
Do we need to hire additional technical staff?
Not usually. Your existing finance team runs the automated system. If you want internal staff to make technical modifications later, someone with database or scripting experience helps but isn't required.

What Clients Actually Say

The questions above come from real conversations. But sometimes it helps to hear from people who've already been through the process.

Below are two of our long-term clients who've agreed to be resources for prospects. They're honest about what worked, what took longer than expected, and what they'd do differently. Not sales pitches — just their real experience with financial automation projects.

Client review meeting discussing automated reporting system
Petra Lundqvist, Finance Director

Petra Lundqvist

Finance Director, Import/Export Company

"We went live in March 2025. The hardest part? Getting our own team to trust the automated numbers. Took three months of parallel checking before everyone relaxed. Now they wonder how we managed manually."

Darko Petrović, CFO

Darko Petrović

CFO, Manufacturing Group

"Started with basic P&L automation in January 2024. Added consolidation reporting six months later. Biggest surprise was how many ad-hoc reports we could automate once the foundation was built. Contact me if you want the unvarnished version."

Still Have Questions?

These answers cover the common scenarios, but your situation might be different. Let's talk about what you're actually dealing with and whether automation makes sense for your specific setup.

Ask Your Specific Question