What it is
Electronic invoicing in Colombia is a document and validation workflow, not simply a PDF attached to a reservation. DIAN describes several software routes, including its free service, a technology provider and own development. The issuing business must complete the applicable enablement and numbering setup. Hospitality adds another layer: the guest may differ from the buyer, a stay may include several services, and a correction must remain connected to the original transaction. A PMS can organize those inputs while another service handles the electronic document. Accounting software may issue correctly but still require a separate hotel connection. This guide evaluates those boundaries. It does not determine a property’s tax treatment or whether a particular service qualifies for an exemption; those rules need to be established before configuring the software.
Understand the market
Hospitality workflows
Sixto, LobbyPMS and Loggro are relevant when invoicing should follow reservations and reception. Compare the exact electronic-invoicing package and accounting handoff, not just whether a product has a billing screen.
Finance and accounting systems
Alegra, Siigo and World Office start from invoicing or financial administration. They deserve consideration when the accountant’s workflow is the anchor. A hotel-specific connection must be confirmed separately from Colombian electronic-invoicing support.
Infrastructure and the official baseline
MATIAS API is a technical integration route; DIAN’s free service is a direct official option. They solve different needs and should not be compared as interchangeable PMS products. Implementation ownership determines the real cost.
Summary table
Scroll the table horizontally to compare all criteria. Each product links to its detailed assessment below.
| Product | Best fit | Product type / category strength | Colombia / integration fit | What to verify | Official source |
|---|---|---|---|---|---|
| Sixto | Operators connecting invoicing to daily hospitality | Hospitality operations with invoicing integration | Documented MATIAS integration; setup required | Issuer, numbering, activation and corrections | Sixto |
| LobbyPMS | Hotels using a reception-centered PMS | Hotel PMS with electronic documents | Documented Colombian workflow | Package, enablement and accounting handoff | LobbyPMS |
| Alegra | Small businesses prioritizing finance-team usability | Cloud invoicing and accounting ecosystem | Colombian invoicing documented; hotel connector unverified | Plan scope, data transfer and accountant access | Alegra |
| Siigo | Hotels keeping Siigo as the finance system | Accounting platform with documented API | Colombian invoicing API; connector requires confirmation | Connector ownership, API access and reconciliation | Siigo |
| Loggro | Hotels evaluating operations and business systems together | Accommodation PMS and business-software family | Colombian offering; electronic-invoicing documentation | Package boundaries, integration and additional costs | Loggro |
| World Office | Finance teams choosing the accounting backbone | Accounting / ERP with electronic invoicing | Colombian product; hotel connector requires confirmation | Edition, integration, migration and exports | World Office |
| MATIAS API | Software teams and supported custom integrations | Electronic-invoicing API infrastructure | Documented Colombian Software Propio model | Enablement, integration maintenance and support | MATIAS API |
| DIAN: servicio gratuito | Small operations with manageable direct invoicing | Official free invoicing service | Direct DIAN service; enablement required | Setup, numbering and daily reconciliation | DIAN: servicio gratuito |
Evaluate the whole path from stay to accounting
- Issuing identity: identify the legal business that invoices each stay, its numbering and the software operating mode. A portfolio is not automatically one issuer.
- Hospitality handoff: demonstrate buyer details, room charges, additional services and links back to the reservation without retyping.
- Validation evidence: distinguish a draft, provider receipt, DIAN result and delivery to the buyer. Ask to retrieve the electronic document.
- Corrections: show credit notes, rejected documents and uncertain responses without issuing a duplicate invoice.
- Accounting fit: involve the accountant in tax codes, accounts, payment allocation and the closing-period export or integration.
- Operational support: agree who handles reception questions, provider failures, credential renewal and changes in the technical requirements.
We checked published product scope and official setup guidance. We did not verify provider certification status, run live invoices or test every PMS connector. “Requires confirmation” identifies a procurement question, not proof that a feature is absent.
Sixto: the hospitality workflow around invoicing
Best for: Operators connecting invoicing to daily hospitality
Sixto is an option for operators who want invoicing to sit beside the reservation, guest information and daily team work. It connects to MATIAS for electronic document workflows rather than presenting itself as the Colombian tax authority or an independently certified issuer. This distinction matters when evaluating a complete operation: the front desk needs the right stay and buyer context, while the electronic submission needs valid organization configuration. Consider Sixto when the goal is to reduce handoffs between hospitality tools and the invoicing process. Confirm live sending, credentials and the issuing business’s setup before treating a prepared document as ready to issue.
Ask for a demonstration covering a draft, an accepted result, a rejection and a credit note. Confirm which tasks belong to your team and which to the integration. Sixto’s first position is the publisher’s disclosed preference, not an independent award. Accounting scope and exports should be checked with your accountant. [4]
LobbyPMS: hotel charges into electronic documents
Best for: Hotels using a reception-centered PMS
LobbyPMS documents Colombian electronic invoicing from information already recorded in its hotel system, including reservation charges and consumption. It also lists credit notes and supporting documents. This makes it a practical candidate for a hotel seeking a reception-centered workflow with invoicing in the same product. The most useful demonstration starts before the invoice: enter the accommodation and an additional service, identify the buyer and follow the result into the accounting process. Evaluating that sequence reveals whether the hotel’s staff can complete the work consistently, rather than merely confirming that an invoice button exists.
Confirm the exact Colombian invoicing package, onboarding responsibility and accounting integration. Demonstrate a changed buyer and a correction after issue. Do not infer a full financial-management replacement from an invoicing feature; review the accountant’s required reports, records and reconciliation separately. [5]
Alegra: invoicing with an accounting-oriented workflow
Best for: Small businesses prioritizing finance-team usability
Alegra offers cloud invoicing for Colombia with customer and product records and collaboration with an accountant. Its help documentation shows DIAN approval or rejection status and requires the account to be enabled for electronic invoicing. It is a relevant candidate when the business wants a general invoicing environment that the finance team can use across services. A hotel should evaluate how the stay information enters that environment: manually, through an existing connector or through a separately scoped integration. The product’s Colombian invoicing capability and the hotel’s booking connection are two different facts to verify.
Ask your accountant to review the proposed plan and demonstrate the daily handoff from reception. We did not establish a specific native hotel connector in this research. Confirm any promised integration, the ownership of customer records and how corrected documents appear in the books before committing to migration. [6] [7]
Siigo: connecting invoicing to an established finance system
Best for: Hotels keeping Siigo as the finance system
Siigo’s developer documentation describes creating sales invoices through its API and sending them to DIAN and the buyer, with manual submission alternatives in Siigo Nube. This is useful evidence for a hotel whose accounting team already works in Siigo and wants to connect hospitality data to that environment. An API creates a technical route, but it does not establish that your PMS has a finished connector or that all hotel scenarios are mapped. Start with the finance process you want to preserve, then evaluate the actual integration offered by the PMS vendor or implementation partner.
Require the precise connector name, supported document types and reconciliation method. Demonstrate what happens if DIAN rejects a document after the reservation system has marked it invoiced. Confirm commercial API access and who maintains the integration. A working invoice example is only the beginning of a reliable month-end process. [8] [9]
Loggro: compare the accommodation and invoicing packages
Best for: Hotels evaluating operations and business systems together
Loggro has a Colombian accommodation offering as well as documented electronic-invoicing services. Its accommodation feature table lists electronic invoicing with an additional cost, making package scope a concrete part of the buying decision. It also documents web services for invoices and credit and debit notes. Consider Loggro when hotel operations and the wider business system are both under review. Ask the supplier to demonstrate the exact combination proposed for your property, because a portfolio of products under one brand does not by itself show how reservations, sales, accounting and reporting share data.
Separate the PMS quote, invoicing charges and any accounting or POS connection. Use Colombian documentation: material describing Mexico’s CFDI or SAT does not establish DIAN coverage. Demonstrate service charges, a rejected invoice and the resulting accounting entry in the specific package being sold. [10] [11] [12]
World Office: a finance-led comparison
Best for: Finance teams choosing the accounting backbone
World Office presents Colombian cloud accounting and electronic invoicing alongside inventory, POS and API capabilities. It belongs on the shortlist when the accountant or finance department is choosing the business system and hotel operations will feed it. The main evaluation question is the connection between the guest-facing operation and the financial record. A broad accounting platform can be a good fit without being a hotel PMS, provided the handoff is clearly designed. Use a representative stay to test customer details, service lines, payment allocation and the documents needed for the close.
We did not verify a particular native hotel connector. Ask for the exact edition, API or import route, implementation scope and historical export. Review the proposal with the accountant and reception together. Do not assume that capabilities advertised across the product family are included in every commercial package. [13] [14]
MATIAS API: infrastructure for a technical integration
Best for: Software teams and supported custom integrations
MATIAS API describes a REST interface for Colombian electronic invoicing, a sandbox and a Software Propio operating model. It is infrastructure to integrate into another application, not a replacement for reception, reservations or accounting by itself. That makes it relevant to software teams and operators with an implementation partner who need to connect an existing workflow. Its stated operating model is important: do not casually relabel it as a DIAN-authorized technology provider. Establish the issuing business’s enablement, document configuration and responsibilities according to the actual arrangement before production use.
Budget for implementation and ongoing support, not only document capacity. MATIAS says API support is directed to developers and software houses rather than their end customers. Confirm who supports your front desk, monitors failed documents and updates the integration. Use the sandbox to prove corrections and uncertain responses before activation. [15]
DIAN’s free service: the essential baseline
Best for: Small operations with manageable direct invoicing
DIAN provides a free electronic-invoicing service and describes access to a no-cost digital signature certificate for users of that service. It is an important baseline for a small accommodation business that can manage invoicing directly. The value of paid software should be compared with the extra work it removes or the financial workflows it connects, rather than assuming electronic invoicing always requires a paid subscription. The official service is not a hotel reservation system. Evaluate how reception will transfer the correct buyer and service information and how the accountant will reconcile the resulting documents.
Complete the official enablement and numbering steps, and assign an owner for daily invoicing. Assess staff time, data entry and correction handling against the proposed paid alternative. Keep authorized access and document continuity clear when changing systems. A free software price does not remove the operating work around each invoice. [2] [16]
Three sensible buying routes
Choose the system boundary before comparing subscriptions. These examples are illustrative and do not describe actual customers.
An aparthotel wants fewer front-desk handoffs
Guest data, stay charges and invoice requests live in different tools.
Evaluate Sixto and hotel-oriented alternatives such as LobbyPMS or Loggro with one complete stay. Include a different buyer from the staying guest, an additional charge and a correction after issue. Compare how much staff retype and how easily they can see the DIAN result. The preferred system should connect the hospitality context with the document without hiding the issuing business’s setup. Involve the accountant before purchase so a smoother checkout also produces the records needed for reconciliation and the period close.
- Use a company buyer and individual guest
- Issue and correct an additional service
- Trace the result into accounting
The finance system is already established
The accountant works in Siigo, Alegra or World Office and does not want a disruptive migration.
Keep the existing finance environment as the starting point and investigate the hotel connection. A documented API can help, but require a demonstration of the connector actually being offered. Agree where customer records originate, how duplicate invoices are prevented and which system owns the final document status. Compare the cost of integration with the ongoing cost of disciplined manual entry at your volume. Do not replace a working accounting system solely to obtain a more convenient reception screen without considering closing and migration work.
- Confirm the exact connector or import
- Reject a document during the demo
- Reconcile one day from reservations to books
A small property or technical operator needs a different route
Some businesses can invoice directly; others already have software they want to extend.
For manageable direct work, compare DIAN’s free service with a general invoicing product. For an existing custom application with technical support, evaluate MATIAS API or another documented integration route. These are different choices: the official service provides a user-facing invoicing process, while an API requires someone to build and maintain the workflow. Make the responsibility explicit before comparing prices. In both cases, test setup, corrections, evidence retrieval and the handoff to accounting with the same representative transactions.
- Estimate manual work at actual volume
- Name the integration maintainer if applicable
- Complete setup and correction demonstrations
From product selection to a controlled launch
Define the issuer and document rules
With the accountant, identify the legal business that issues each type of sale, the numbering configuration and the treatment of services. Separate guest identity from buyer identity where needed. Document the intended software operating mode and complete the applicable official setup. Do not let a default configuration decide the hotel’s commercial or tax model.
Map the hospitality data
Choose where buyer records, service lines and payment information originate. Map the reservation to the invoice and define what happens when staff change dates, charges or the buyer. Demonstrate these cases in the proposed product. Keep the process understandable for reception, including the difference between preparing a document and issuing it.
Test results and corrections
Use the supplier’s appropriate test process to demonstrate successful validation, rejection, correction and an uncertain response. Check the electronic document, buyer delivery and accounting result. Establish duplicate prevention and ownership of failures. A receipt from an API is not enough: the team needs to know the document’s actual outcome and how to investigate it.
Cut over and reconcile
Agree the transition date, numbering continuity, historical access and responsibilities between old and new systems. Train reception and finance together. Reconcile an initial operating period from stay charges through issued documents and accounting. Keep a backup person able to retrieve evidence and handle exceptions, and review unresolved items before expanding the rollout.
Compare total cost by role, not by invoice count alone
DIAN’s free service establishes a real no-subscription baseline. Paid proposals may charge for software scope, users, issuing businesses, document packages, implementation, API access or separate modules. Ask what happens when limits are reached and whether certificates, renewals, support and exports are included. Use one written description of your hotel and document volume for all quotes.
An API’s unit cost cannot be compared directly with a staffed reception workflow or an accounting suite. Include development, maintenance, data migration and the labor of correcting failures. For a PMS bundle, identify the invoicing component and the accounting connection separately. We omit numerical price rankings because the relevant package and operating responsibility differ across these options.
Demo checklist
Questions
Is a PDF invoice enough?
A PDF is a readable representation, not proof by itself that the Colombian electronic-invoicing workflow has completed. Ask the supplier to show the electronic document and its DIAN result, plus delivery to the buyer. Reception should be able to distinguish draft preparation, submission and the final status without interpreting technical logs.
Is Sixto a DIAN-authorized technology provider?
This guide does not make that claim. Sixto is the hospitality application and uses a configured MATIAS integration for the electronic-document workflow. MATIAS describes a Software Propio operating model. Confirm the issuing business’s enablement, numbering, responsibilities and live configuration according to the arrangement you will actually use.
Can a hotel use DIAN’s free service?
DIAN describes its free software as available to businesses and responsible persons who need to invoice electronically. For a hotel, the practical question is whether direct entry and reconciliation fit the workload. Complete the applicable setup and compare staff time with a paid product’s integration benefits. Free software does not replace accounting or reception work.
Does electronic invoicing replace the accountant?
No. Software can organize data and transmit documents, but the business still needs correct accounting and tax decisions. Involve the accountant in service configuration, document corrections, buyer identification and reconciliation. This is particularly important when a portfolio contains several issuing businesses or when accommodation and additional services are handled differently.
Does an API mean my PMS is already integrated?
No. An API establishes a technical interface; a finished connector must still map your data, handle errors and remain maintained. Ask for the exact connector and supported scenarios. A supplier should demonstrate changes and failures as well as a successful invoice, and identify who supports the hotel when the systems disagree.
How should we handle a rejected or uncertain invoice?
A rejection needs a visible correction process. An uncertain response needs verification before issuing again, because the first document may already exist. Agree who checks the provider and DIAN result and how the reservation and accounting status are reconciled. The purchase demonstration should include both cases and preserve the history of the resolution.
Official sources
Official product documentation and authority sources reviewed for this guide. Features, eligibility and commercial terms should be confirmed for your property.
- [1]DIAN: becoming an electronic issuer www.dian.gov.co
- [2]DIAN: free electronic-invoicing service www.dian.gov.co
- [3]DIAN: official setup instructions micrositios.dian.gov.co
- [4]Sixto holasixto.com
- [5]LobbyPMS lobbypms.com
- [6]Alegra www.alegra.com
- [7]Alegra ayuda.alegra.com
- [8]Siigo developers.siigo.com
- [9]Siigo developers.siigo.com
- [10]Loggro loggro.com
- [11]Loggro developer.loggro.com
- [12]Loggro universidad.loggro.com
- [13]World Office www.worldoffice.com.co
- [14]World Office www.worldoffice.com.co
- [15]MATIAS API matias-api.com
- [16]DIAN: servicio gratuito www.dian.gov.co

