Complete SaaS ERP Solution for Tax/Accounting Firm

Hi Dana,

To prepare an accurate proposal and development roadmap, we'd appreciate clarification on the following:

1. Do you already have functional specifications or wireframes for the platform?

2. Should the mobile application include the full ERP functionality or focus primarily on client-facing features?

3. Which payment gateway(s) and banking providers will need to be integrated?

4. Do you already have access to AEAT and INTRASTAT integration specifications or existing API credentials?

5. Will third-party accounting software integration (e.g., Sage, A3, Holded, SAP, Microsoft Dynamics) be required?

6. Is this intended as a single-company solution or a multi-tenant SaaS platform serving multiple accounting firms?

Looking forward to your response.

- Regarding AEAT integration, should the platform automatically generate, validate, submit, and track the status of all required tax models, or will some filings be reviewed manually before submission? Additionally, should the system support automatic updates for future regulatory changes, digital certificates, electronic signatures, submission acknowledgements, and error handling for rejected filings?

- How would you like the secure client portal to function? Should clients be able to upload documents, organize files into categories, receive notifications, digitally sign contracts, communicate with assigned accountants, monitor filing status, download completed tax documents, and maintain a complete history of all submissions and financial records?

- For the INTRASTAT and customs module, should the platform automatically classify products using CN8 codes, validate declaration data, generate required reports, and submit declarations directly to the relevant authorities? Additionally, are there other international tax workflows, customs procedures, or cross-border reporting requirements beyond the listed models that should be included in the initial release?

1: Given the breadth of AEAT models, SII, INTRASTAT, customs, non-resident taxation, and PSD2 requirements, do you expect the first release to achieve full regulatory coverage from day one, or would you prefer a phased rollout prioritising the highest-value compliance modules while keeping the architecture extensible for future additions?

2: Will this ERP become the firm's primary system of record, or should it coexist with existing accounting, banking, or document-management platforms? Understanding where the source of truth resides will determine how the APIs, synchronisation strategy, and data model should be designed.

3: Is your objective to build an internal platform exclusively for your consultancy, or are you intentionally designing this as a multi-tenant SaaS product that can later be licensed to other tax and accounting firms? That single decision will influence the tenancy model, permissions, billing architecture, and long-term scalability from the outset.