I would like documentation for csv Import, Line 50

[HeinzKiosk]

I considered downloading the free Line50 sample from this site, which doubtless contains a help file with the answer in it, but that felt a bit dishonest as I have no intention of buying a copy of Sage. Let me know if the site owners don't mind me doing that...

I'm a developer of a package some of whose users want to import figures from the package into their copies of Sage. It wouldn't be SL or PL related. It would either be bank payments with an associated nominal journal, or just a nominal journal, typically with 10-20 lines in it.

I can't find Sage's requirements for import anywhere online, and hoped that someone could tell me what the csv should look like, and what restrictions there are on the fields. A sample csv of nominal journal or payment+journal would be great.

Thank you. Any help or guidance will be gratefully received.

[brucedenney]

There is a clunky, manual, user process that allows invoices to be imported into the customer ledger, however, this does not give full drill down, you need to get all users out of the system to run it, you run the risk of users importing the wrong batch, double importing, missing a batch importing in the wrong order and so on.

There is some information on our support site, however, sage have switched a few fields around between different versions in some of the files. If you want to let me know the version you are developing for I can probably sort something out for you.

http://sage.support.makingithappen.co.uk/importing.htm

We have an integration service/product that would enables us to put just about any data into Line 50 so we could put them in the invoicing module and so allow them to have full drill down etc, we can also make it a single click or even zero click process, and allow it to run with other users logged in, the file you create would be the same regardless of what version of Line 50 you were linking to.

The cost of such a solution is likely to be around £360, this would include the custom code for your package, additional purchases for other users would be £225.

Use the contact form if you want to get more information on this option.
http://www.makingithappen.co.uk/feedback.htm

[HeinzKiosk]

Thank you very much for your prompt response. I've been otherwise engaged for a couple of days. Perhaps I should explain some background. My company's software is a payroll:

http://www.12pay.co.uk

We give the basic version of our software away, and we only charge £40/year for the premium version. So attempting to sell Sage integration to our users for £225 would be completely out of line with the cost of our package. A couple of our users have asked if we integrate with Sage Line 50, and doubtless there are more. We would be looking to bundle this feature in with our premium offering.

What we need is once/week or once/month to be able to import one small nominal ledger journal into Sage, something like:

Dr payroll expense
Dr employer's NI
Dr assorted codes representing other payments
Cr PAYE/NI liability
Cr Net Pay liability OR Bank Account

The above perhaps going to more lines if departmental subanalysis is required.

Some of the objections with standard Sage import that you mention (such as single-user only) are probably irrelevant in this context. But clearly different Versions of Line 50 may be a big issue, as we cannot say which version our users would have. OTOH we wouldn't have a problem with stating that they must have the current version to use our (limited) integration, so a file format for that would probably be fine.

[brucedenney]

It is your lucky day, the audit trail transaction format is the same in all vrsions of line 50.

You just need to create a CSV file and tell the user to import it.

Here is the spec for the file.

http://sage.support.makingithappen.co.u ... ttrans.htm

[HeinzKiosk]

That data looks absolutely perfect. Thank you very much for your kind help.

[HeinzKiosk]

Thanks for your help.

I've managed to create a file which goes into Line 50. I'm hoping that Instant Accounts accepts the same format too.

I just used JD and JC, and left the account blank, only filling in nominal codes and departments,reference and value with an exchange rate of 1. That seemed to work fine.