Faith Forge LabsChile
EnglishEspañol

Discover the invoicing route before promising a DTE connection

An office wants approved job information to reach its electronic invoicing process. “Connect to the SII” is not yet a technical scope. The organization may use the SII’s own system, a market product or another approved arrangement, and the available interface depends on that actual route.

This fictional discovery ends with a defined staff handoff because the first proposed automatic connection is not supported by the inspected setup.

Name the current system and its owner

The fictional business records jobs in Tool A and uses the SII’s free invoicing system for its existing process. Its accountant approves what information is needed and which person may perform the invoicing task.

The SII’s system comparison distinguishes its free platform from own or market systems. The comparison states that the free platform does not integrate with the taxpayer’s applications. That narrow point is relevant to this discovery; it does not decide whether the business should change its invoicing arrangement.

A product demonstration or a developer’s access to a website is not evidence of an approved automatic interface.

Separate the desired outcome from the assumed connector

The office’s actual objective is to avoid reconstructing approved work from several job screens. A direct connector is one possible means, but the useful first result is a complete, reviewable set of information for the authorized invoicing task.

For fictional job J-67, the accountant specifies an approved transfer worksheet containing the job reference and the required business information. The developer does not choose fiscal classifications or infer tax treatment from a service name.

The office reviewer confirms that J-67 is eligible for the handoff. A completed field visit alone does not make it eligible.

Choose a supported first phase

The team selects a structured export from Tool A for staff review. It contains the approved information and stable job reference, with an explicit “prepared for invoicing review” state.

The export does not mark a document issued. After the authorized staff member completes the appropriate process in the invoicing system, the office records the resulting reference through its agreed reconciliation procedure.

No screen scraping or imitation of a user session is added to bypass the missing supported connection. A future provider change would require fresh inspection and professional approval.

Rehearse without issuing a real fiscal document

In private review, J-67 produces the expected transfer worksheet. A job J-68 that lacks office approval does not enter the eligible set. A second eligible job retains its own reference and values.

The reviewer also checks an incomplete worksheet. It remains awaiting correction rather than being marked transferred. The rehearsal uses fictional records and suitable test facilities; it does not create live fiscal documents to prove the export works.

The acceptance record ends at the approved technical boundary: staff can obtain and review the information. It does not claim that a real invoice was issued or accepted by an authority.

Keep the future decision explicit

If the organization later adopts a market system with a supported interface, discovery should inspect its account permissions, test environment, document states and reconciliation operations. The accountant and provider approve the required process.

The first phase is useful because it improves the existing handoff while preserving the actual system boundary. Bring your chosen invoicing route and the colleague responsible for it to a business connection discussion.