nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Printing Payslips error

Gayle_10863666

Could anyone tell me how to fix the below printing of payslips please, I have spent a lot a time thinking it is a printer setting, but can't seem to fix it or work out how it has changed. First screen shot is how it was printing, second screen shot is how it is now printing - Thank you Gayle

Accepted answers

Rav

Hey @Gayle_10863666

Just a quick update, our dev team has acknowledged this issue and they can replicate it themselves as well.

The issue only affects the label names, but the employee data itself is not impacted and is correct.

They're working on a fix to address this which will come through in Reckon One's next update and I'll keep you posted on that.

All comments

Rav

Hi @Gayle_10863666

Thanks for flagging this, it definitely looks like a strange one. Did this just start happening today?

Can I just confirm, is this occurring on all employee payslips that you attempt to print or just a specific employee?

Also, are you printing multiple payslips in one go or just one-at-a-time?

Lastly, are you printing in portrait or landscape orientation when you notice this happening?

Gayle_10863666

Hello Rav, yes it started happening today, the screen shot of the one that is OK is from previous pay run.

Every payslip (41 of them) are the same.

Printing one at a time (majority of mine are 2 pages, duplex doesn't work with bulk printing) it doesn't know when to start a new page :)

Printing them all Portrait.

Rav

Thanks for that @Gayle_10863666

I've just had a look at my own test book and I can see the same thing happening as well so its not something on your end. Leave this with me for a bit and I'll have a chat with the dev team about this.

Will come back to you

Rav

Hey @Gayle_10863666

Just a quick update, our dev team has acknowledged this issue and they can replicate it themselves as well.

The issue only affects the label names, but the employee data itself is not impacted and is correct.

They're working on a fix to address this which will come through in Reckon One's next update and I'll keep you posted on that.