Built by people who knew the close-cycle firsthand.
Centinel began in 2025 in Barcelona, founded by people with years in finance operations and ERP infrastructure. We watched the same journal entry issues appear at month end. The answer is not another spreadsheet, but evaluation when entries are posted.
ERP close cycles remain a manual hunt through a month of entries.
Finance teams on major ERPs face a basic gap: entries post throughout the month, while review waits for close. By day one, thousands may need checking, including a few material errors. Finding them depends largely on experience and chance.
Controllers rely on spreadsheet checklists, while auditors review samples. Everyone hopes important issues appear before sign-off. If they do not, the result may be restatements, audit findings, or days added to close after a day-three discovery requires investigation.
Centinel shifts review from month end to entry posting. Each entry is checked against your rules in real time. Exceptions appear as soon as they arise, not when someone searches. Close starts with a clean view.
People who have faced the problem firsthand.
Tomas Clark
CEO & Co-Founder
Tomas brings a financial controls and ERP audit automation background, with experience creating reconciliation workflows for mid-market finance teams in manufacturing and distribution. He started Centinel after seeing close-cycle exceptions recur across engagements.
Marcus Reinholt
CTO
Marcus has a distributed systems background, building real-time data pipelines and event-streaming infrastructure for financial platforms at scale. He applied that infrastructure expertise to Centinel's journal entry evaluation challenge.
Nina Ferreira
Head of Customer Success
Nina brings finance operations and ERP implementation experience across NetSuite and SAP environments. She helps controller teams set rules, connect ERPs, and realize value from Centinel during their first close cycle.
Principles guiding us.
Coverage over hope
Controls break down when sampling and experience carry the burden of finding exceptions. We favor systematic coverage: every entry, every period, without gaps.
Always read-only
Centinel never writes to your ERP. A financial auditing tool should not be able to alter the data it reviews. That is built into the product, not left to configuration.
Fast value
Controllers cannot spend a month on implementation. Centinel connects in under 15 minutes and shows real exception data during the first close cycle. No consulting engagement is needed.
Evidence over claims
Each exception detection, assignment, and resolution receives a timestamped log. Close packages contain the exception history, giving audit committees and external auditors documented evidence rather than verbal assurance.
Ready to speak with the team?
Questions about your ERP setup or close-cycle needs? We would be glad to discuss how Centinel can fit your process.