Choosing an API Verifactu starts with understanding what your application needs. A demonstration with a simple invoice is useful, but it does not represent the daily work of an ERP, an accounting practice or a SaaS platform. Before deciding, list your real operations and turn them into a small validation project.
Define the operations you need
List the issuing businesses, the document types your business uses and the data your software already stores. Identify who will review incidents as well. This helps establish whether the API covers your workflow and which tasks remain your application's responsibility. Connecting a service does not replace a review of the complete invoicing system.
Evaluate documentation with a real use case
Look for authentication examples, complete requests and error responses. Our documentation provides API v2 operations, data tables and Postman collections. Ask the technical team to confirm anything the contract does not specify; an assumed header or retry mechanism can become an incident that is difficult to reproduce.
Check traceability and maintenance
Your team should be able to connect the local invoice to the submitted request and the result received. Assess how to query statuses, recover an uncertain operation and handle version changes. AEAT publishes VERI*FACTU technical information; use it as a reference when placing the integration within the complete system.
- Prepare a successful case and a rejected validation case.
- Check what happens when the connection is interrupted.
- Assign someone to review incidents.
- Document how the connector is updated and maintained.
Compare cost against expected usage
Review current licensing, volume and support conditions alongside integration and maintenance effort. A useful comparison connects price to the businesses issuing documents and their expected activity. Start with the pricing page and validate your scenario in testing before planning deployment.