Index
What is this integration?
The Sage Murano 200 integration lets you move Golfmanager invoices and payments into your accounting without typing them in by hand. Golfmanager generates an Excel file with the accounting entries, ready to import into Sage Murano 200 (Sage's management and accounting ERP).
Sage Murano 200 is a business management ERP. Unlike other exports that generate a text file, this one generates an Excel file (.xlsx) with an "Asientos" (journal entries) sheet that Sage Murano can import.
What problem does it solve?
Eliminates manual entry of invoices and payments into the accounting.
Reduces typing errors in amounts, accounts and VAT.
Saves time at the monthly or quarterly close.
Keeps consistency between what is invoiced in Golfmanager and what is recorded in Sage Murano.
Which systems does it connect and in which direction does the data travel?
The integration works in one direction only: from Golfmanager to Sage Murano.
It is an on-demand export: you select the invoices or payments and generate the Excel when you need it.
Sage Murano does not return information to Golfmanager.
The "bridge" is the Excel file that Golfmanager downloads and that is then imported into Sage Murano.
What information is exported?
Export | What it contains |
Invoices | The invoice entries (customer account, income by subfamily and VAT) in an Excel |
Payments | The payments/collections, in an Excel (can be grouped by company) |
The Excel includes an "Asientos" sheet with, for each invoice, the customer line (in the Debit) and the income by subfamily and VAT lines (in the Credit), together with data such as the company code, the delegation, the dates, the invoice type and the territory code.
Prerequisites (before enabling the integration)
Have invoicing active in Golfmanager.
Have the Sage Murano 200 module installed (see below).
Invoicing permissions to access the export.
Know how the accounting is set up in Sage Murano (accounts, company code, delegation and territory).
Authorization form
To authorize the integration between your company and the system through an API, you normally need to send Golfmanager a document filled in and signed by both parties before you start. Your implementation team will tell you the specific form and how to submit it.
Installing the module
To use this functionality you need to contract the module and download it from the App Market. If it is not available to you, contact our support team through the blue bubble in your management software.
Once installed, the configuration section in Invoicing and the export actions in the invoice and payment lists will appear.
How to set it up (step by step)
It is best to fill in these data before exporting, ideally just once and together with your accountant.
Step 1 — General configuration
Settings Menu > Invoicing > Settings > "Sage Murano Settings" section
Go to Settings Menu > Invoicing > Settings.
Find the Sage Murano Settings section.
Check Entry per invoice if you want an accounting entry to be generated for each invoice.
Fill in the default accounts (mandatory): Default customer accounting account, Default tax accounting account and Default subfamily accounting account.
Indicate the Invoice type and the Territory code for Sage Murano.
Save the changes.
Step 2 — Per-company data
In each company, enter its Sage Murano Code and its Sage Delegation ID.
Save.
Step 3 — Specific accounting accounts (recommended)
If you do not want to always use the default accounts, assign the specific accounting account where applicable: in the customer record, in the product/subfamily, in the tax and in the payment method. The system uses the specific account if it exists and, failing that, the default account from Step 1.
Step 4 — Exportable invoice types
In each invoice type that should be recorded, check Export to Sage Murano.
⚠️ If an invoice is not exported, it is usually because its invoice type is not marked as "Export to Sage Murano" or because the invoice was already marked as exported.
The configuration fields in detail
Below is an explanation of each field involved in the export.
1) Entry per invoice
• Field name: Entry per invoice
• Description: A checkbox indicating whether a separate accounting entry is generated for each invoice (instead of grouping several into the same entry).
• Impact on the system: It determines how the entries are numbered and grouped in the Excel.
• Usage example: you check it if your accountant wants one entry per invoice.
What happens when it is used: each invoice generates its own entry number (incrementing).
System behavior: if not checked, invoices may share an entry according to the grouping criteria.
2) Default customer accounting account
• Field name: Default customer accounting account
• Description: The customer account used when the customer does not have their own account assigned.
• Impact on the system: It ensures the customer line is never left without an account in the Excel.
• Usage example: you enter 43000000 as the default account.
What happens when it is used: invoices of customers without their own account come out with that account.
System behavior: it uses the customer's account if it exists and, if not, this default one.
3) Default tax accounting account
• Field name: Default tax accounting account
• Description: The VAT/tax account used when the tax does not have its own account.
• Impact on the system: It ensures the VAT lines come out with an account.
• Usage example: you enter the default output VAT account.
What happens when it is used: VAT lines without a specific account use this one.
System behavior: the tax's account takes priority if it is defined.
4) Default subfamily accounting account
• Field name: Default subfamily accounting account
• Description: The default income account when the product/subfamily does not have its own account.
• Impact on the system: It ensures the income bases come out with an account.
• Usage example: you enter a generic sales account.
What happens when it is used: products without a specific account use this one.
System behavior: the product/subfamily account prevails if it is defined.
5) Invoice type
• Field name: Invoice type
• Description: The invoice type code that Sage Murano expects in the entry.
• Impact on the system: It classifies the document in Sage Murano.
• Usage example: the one your accountant indicates for their sales invoices.
What happens when it is used: the Excel comes out with that invoice type.
System behavior: an incorrect value may cause errors when importing into Sage.
6) Territory code
• Field name: Territory code
• Description: The territory/region code that Sage Murano requires.
• Impact on the system: It accompanies the entries in the Excel for correct tax classification.
• Usage example: the one your accountant indicates.
What happens when it is used: the Excel includes that territory code.
System behavior: if it is missing or wrong, Sage may reject the import.
7) Sage Murano Code (company)
• Field name: Sage Murano Code, in each company
• Description: The code under which that company is registered in Sage Murano.
• Impact on the system: It identifies which Sage company the entries belong to.
• Usage example: your accountant provides it for each company.
What happens when it is used: the Excel comes out with the correct company code.
System behavior: without it, entries may go to the wrong company or fail.
8) Sage Delegation ID (company)
• Field name: Sage Delegation ID, in each company
• Description: The identifier of that company's delegation in Sage Murano.
• Impact on the system: It associates the entries with the correct delegation.
• Usage example: your accountant provides it if you work with delegations.
What happens when it is used: the Excel includes that delegation in each entry.
System behavior: useful when a company has several delegations.
9) Export to Sage Murano (invoice type)
• Field name: Export to Sage Murano, in each invoice type
• Description: Marks which invoice types are exportable to Sage Murano.
• Impact on the system: Only invoices whose type is marked are exported.
• Usage example: you check the "Sales invoice" type and leave unchecked the types you do not record here.
What happens when it is used: invoices of that type are included in the export.
System behavior: invoices of unmarked types are ignored in the export.
10) Exported to Sage Murano (invoice / payment)
• Field name: Exported to Sage Murano (in the invoice or payment detail)
• Description: An indicator (No / Yes) showing whether it has already been included in an export. The system updates it.
• Impact on the system: It avoids exporting the same thing twice; only what is in "No" is exported.
• Usage example: you generate the Excel including invoice no. 2025/0123.
What happens when it is used: that invoice automatically changes from No to Yes.
System behavior: you can set it back to No with "Reset Sage Murano export status" to re-export.
ℹ️ Note: the exact names may vary slightly depending on your version and language. The function of each field is as described.
How it is used day to day
Exporting invoices to Sage Murano
Go to the Main Menu > Invoicing > Invoices.
Mark the reference of the invoices you want to export.
Select Actions > Export excel Sage Murano (in the "More" menu).
In the pop-up, enter the Entry number the export should start with.
Click Accept.
An Excel file is downloaded automatically (for example,
facturas_….xlsx).Import the Excel into Sage Murano (usually done by the accountant).
Check: in each invoice's detail, the Exported to Sage Murano field will have changed from No to Yes.
Exporting payments to Sage Murano
Go to the Main Menu > Invoicing > Payments.
Mark the reference of the payments you want to export.
Select Actions > Export excel Sage Murano.
Enter the Entry number and click Accept.
An Excel of payments is downloaded (for example,
cobros_….xlsx); it can be grouped by company.In each payment's detail, Exported to Sage Murano will change from No to Yes.
Re-exporting (reset)
If you need to repeat an export, select the invoices or payments and use the "Reset Sage Murano export status" action: they will go back to Not exported and you can export them again.
What is exported and duplicate control
To avoid duplicating in Sage Murano, the export only includes:
Invoices of a type marked as "Export to Sage Murano".
Invoices that have not yet been exported ("Exported to Sage Murano" field set to No).
After exporting, those invoices are left as "Exported to Sage Murano = Yes". If you select already-exported invoices, the system warns you that they were already exported. You can set them back to No (or use "Reset Sage Murano export status") to export them again.
Limitations to keep in mind
It is a manual, one-way export. It is not automatic or real-time.
Only the marked invoice types are exported.
The quality depends on the configuration (default accounts, company code, delegation, territory).
Invoices/payments are marked as exported; avoid re-exporting without control to prevent duplicates.
It affects invoicing only, not the booking portal or other areas.
Frequently asked questions
What format is the file generated in?
In Excel (.xlsx), with a sheet called "Asientos" that Sage Murano can import. It is not a text file like other accounting integrations.
Is the export automatic?
No. It is manual and on demand: you choose the invoices or payments and generate the Excel when you need it (for example, at the close of each month or quarter).
How do I install the module?
It is contracted and downloaded from the App Market. If you do not see it available, contact support through the blue bubble.
What is the "Entry number" it asks for when exporting?
It is the number the entry numbering will start with in the Excel. You must indicate the one that corresponds according to your accounting in Sage Murano.
An invoice is not exported. Why?
The most common cause is that its invoice type is not marked as "Export to Sage Murano", or that the invoice was already exported ("Exported to Sage Murano" field set to Yes).
The export comes out empty.
It is usually because everything was already exported or because no invoice type is marked as exportable. Use "Reset Sage Murano export status" or mark the invoice type.
Incorrect or empty accounts appear in the Excel.
Accounts are missing: check the default accounts (customer, taxes, subfamily), the company code, the delegation and the specific accounts on the customer, product, tax or payment method.
Duplicate data appears in Sage Murano.
It was re-exported without control. Do not reset or re-export unless necessary, and coordinate with your accountant to avoid duplicate entries.
How do I know which invoices/payments I have already exported?
In each invoice's or payment's detail, the Exported to Sage Murano field shows No or Yes.
Can I also export payments, not just invoices?
Yes. From Invoicing > Payments, with the same "Export excel Sage Murano" action. The payments Excel can be grouped by company.
Does Sage Murano return any data to Golfmanager?
No. The integration is one-way: from Golfmanager to Sage Murano via the Excel.
Who imports the Excel into Sage Murano?
It is usually done by your accountant, who is the one managing the accounting in Sage Murano.
Recommended best practices
Agree with your accountant on the accounts, the company code, the delegation and the territory before you start.
Mark only the invoice types that should be recorded in Sage Murano.
Export by closed periods and save each Excel identifying the period and the entry number used.
Run a first test with a few invoices and validate it in Sage Murano before adopting the procedure.
Rely on the "Exported to Sage Murano" field to track what has been sent and avoid duplicates.
Need help?
If you have questions about installing the module, configuring accounts or the Excel format, our support team is available to help you. Write to us through the blue bubble in your management software. For the specific accounts, company code, delegation and territory, also rely on your accountant, who is the one who defines how the accounting should look in Sage Murano.