Suggest we have a licensing parent section for this article

Not language a typical user will understand

Again not kb user facing language

Again not user facing language

Lots of overlap between this and the other articles in this section. Unclear what our goal here is with these articles.

Would it be better to list out some commonly used reports? I'm not sure there's huge value in generic articles on reporting - the UI should be self-explanatory

I've noticed these fake screenshots - we need real screenshots or videos

why would htey need to 'check' the result? don't they trust the output?

Can we make this the first article in the 'month end' section?

Is this a daily process?

Very internal facing language - again all language in this kb needs to be user facing.

I don't think this is an every day task - it's more of a an exceptional case that happens from an every day task. suggest it lives in teh reference section but is linked to from the 'post transactions to other systems' every day task article

This type of recommendation should be a link to either 'getting help' doc or a direct link to the support portal

This style of language is not appropriate for end users

Any 'Steps' like these should have screenshots or [even better] quick videos

Suggest re-parenting this to a 'hosted / managed / azure service' topic

suggest re-parenting to a 'getting help' parent section.

although - if they can't log into the help portal, they won't be able to see this doc, so not sure how valuable it is?

Suggest a different parent section for this - getting help

I think the company and currency rule is probably better in this section

should this and the 'life of an account' article be in the previous ' how money flows' section?

this seems to be mixing a few concepts together - th company and currency rule are quite specific where as the hwo clients and accounts relate is more general. suggest splitting them.

I think we should rename this to 'how money flows' or similar and then move the modules doc out of it - everything else is about moving money through the system and not really about how vault is organised.

plus we could add a section in here on 'posting instalments / interest etc.' i.e. vault generated money

this section should be all the [high level] explaining docs behind this picture: https://show.zoho.com/show/open/bvdhvcc22707a420942edb16afb1cfaf383b6/slide/a9c96a7f-f8ee-405a-93ec-7cc8994219f7

the titles in the boxes below are cut off - not sure if that'll be true in zoho desk (or if we can even structure the pages like this?) but we should ensure no cut offs in titles.

diagram required

this is quite verbose language - hard to read... need plainer language across the board. less is more!

this is very internal facing language - I think we need a style guide written up for claude to validate language against.

money?

I'm not sure the 'where you see it' section is helpful in these very high level getting started docs - e.g. in this doc, the 'how info flows' is pervasive to nearly the entire app, so not that helpful.

feels like a good article that could use a diagram or two

we should link terms like these to a glossary or use the html definition tag to define them

this is referencing an internal document - our user facing content should never do that

yes

yes, customers can add modules mid-year

we should this style of writing of talking about users in the third person

is this true? we use the word ledger quite differently afaik

I think we need a 'what is vault' section first before we get into the 'how is it organised' i.e. what is it, what are the benefits, what can you do with it, who's it for etc.

is this a phrase users will be familiar with - can we simplify to plainer english?